JNOTE: As you are reading this, I must have forgotten to set the help topic Jfor the current context! So please tell me where you selected help and got this page! See also: Help contents Hoops you shouldn't be able to enter the help system during dragging... Joops I didn't realise I was using these commands where you can enter the help system... Main Menu General Overview shows the overview info list that is automatic- ally shown at startup Hardware/System Operating System Memory submenus for related information items Software Drives Configuration Files Options... opens a dialog with options for agSI About agSI closes an info window to show the logo and version that appear on the background Help contents opens a help window with the respective page Help index Register! lets you enter your registration info (if not done already) Exit exits agSI Options... JThis menu item opens a dialog window where you can change some settings of +agSI, e.g. continuous information updating. See also: options dialog main menu About the Author GThis menu item opens a help screen with information about the author of agSI. See also: main menu LHelp Contents Ctrl-F1 AOpens a help screen containing the contents' list of agSI's help. See also: main menu LHelp Index Shift-F1 EOpens a help screen containing the alphabetical index of agSI's help. See also: main menu Register! JOpens a dialog window where you can enter your registration name and code. See also: %license and registration information help contents main menu LExit Alt-X NThis menu item quits agSI and returns "But now it's time to be gone/ >to DOS or the calling program. La la la la..."8 Queen, March Of The: Black Queen , 1974 See also: main menu LBack Esc 4This menu item lets you return to the previous menu. About agSI IThis menu option will just close any info window to the right in order to ,clear the view on the agSI logo and version. See also: Main menu The Author of agSI [tadaa!] Andreas Gr Internet e-mail address: ag@studbox.uni-stuttgart.de ( -and groegeas@cip.mathematik.uni-stuttgart.de "Snail mail" address: Andreas Gr gel Gildenstr. 4 D-74074 Heilbronn Germany KIf you encounter any problem with agSI as it is partially programmed very Jclose to the hardware and uses several undocumented things, this is pretty Jlikely (I can't test hundreds of systems and configurations) or anything( Jyou don't like, tell me; only this way agSI can be more and more improved. KEven if you don't have problems with agSI and just want to praise it, don't Hhesitate... most of the mails I get are from people who do have problems with this program... LAll suggestions, proposals, recommendations, advice, solutions, ideas, tips, Khints, aid, help, support, advice, contributions, regrets, appeals, critic- Fism, compliments, eulogies, censure, praise, curses, enquiries, pleas, Kpreaches, requests, petitions, demands, questions, answers, notes, remarks, ]comments, notifications, information, news, reports, articulations, communication, statements FDREAD.COM TSR to allow DOS to read high-capacity floppies 8(taken from the FDFORMAT 1.8 package by C.H.Hochst tter, make some information about parts of Windows available to agSI; see below for a list. KYou may execute AGSIWINS the usual ways: through the File Manager, the Pro- Kgram Manager File|Run menu, or create an icon in a Program Manager group of Kyour choice (or use any other way you are using to start Windows programs). KIf you include command line parameters, most will be passed on to AGSI.EXE. GagSI\WinServ communicates with agSI through the Windows clipboard (in a Lself-defined format); this is a slow but safe way [and a direct call in pro-8 Itected mode from DOS to Windows doesn't work, anyway]. agSI\WinServ keeps. Jlooking for a command in the clipboard which agSI puts there, does what is2 Kwanted and puts the reply to the clipboard where agSI is waiting for it; if Lit doesn't arrive within five seconds (if your system load is heavy, for ex- Kample, or the DOS box has too bad a fore-/background priority setting ( Kfile/Settings); recommended is much more than the DOS-default 100/50)), the Ccommunication "times out"; re-select the menu item to try it again. JWhen agSI exits (normally or with a run-time error), it tells agSI\WinServ Lto quit also; should agSI crash (or report a DPMI error), WinServ keeps run- ning. The WinServ window displays the clipboard format (in the bottom line) which is passed on to AGSI.EXE with the /W command line switch; the current activity in black ("snooping" if waiting for a command in the :clipboard), and the previous (completed) activity in grey. $Also, some menu options are offered: 'File' menu: Start new DOS-agSI starts a new copy of AGSI.EXE in a new DOS window. Exit WinServ exits WinServ; any DOS-agSI keeps running and will not be #able to get the WinServ info items. Options menu: active: Uncheck this to deactivate WinServ's communication function so Dthat DOS-agSI won't get any answers... (May be used to reduce system load.) Exit on DOS-agSI exit: If checked, WinServ exits when an agSI DOS windowC Gexits; it is automatically unchecked when you start a new DOS-agSI from the File menu. Help menu: About WinServ displays an About dialog. Notes: You can't run agSI\WinServ more than once at the same time; when you try Ithat, the already-active window just pops to the front. You can, however, Irun several copies of DOS-agSI, but that is not recommended, and not nec- cessary, anyway. This mechanism is designed to operate in Windows 3.1x enhanced mode (and Halso works under Windows 0.95); it probably won't work in standard mode. 3List of information items provided by agSI\WinServ: Windows version (as told by Windows), flags, and directories Win32s version free heap memory and resources tasks and modules Paging file (swap file) SHELL module (multitasking info) See also: Help Contents Welcome to agSI -SystemInfo- KThis screen shows a general overview which gives you a brief overview about %what agSI can tell about your system. 4If you want to read more about this overview screen: General Overview ,To learn more about this program, see the... Help Contents 8(Press F1 again to see how to operate this help system.) See also: main menu General Overview KThis menu item shows a brief 16-line summary of some things in your system. See also: General Overview info list main menu General Overview JPlease note: This is just a brief overview about some aspects of your sys- Item. Inside the five main menus, hundreds of detailed items can be found. CPU: The type of your processor, plus "V86" if it is in Virtual8086-mode. @(Clock speed and FPU (math coprocessor) are not displayed here.) Cache: If present (and enabled and detected by agSI), this shows the sizes Iof the Level 1 (data cache only, not code cache) and Level 2 cache in KB. BIOS: This tells the manufacturer (if detected) and date of your ROM BIOS. Ports: Number of parallel (LPT) and serial (COM) ports. Graphics: Type of the video chipset, its memory size, and its DAC. ?(using only old method under Windows or OS/2 with less details) Sound: If detected, your sound card: Sound Blaster compatible, MPU-401, (and Gravis UltraSound are detected here. OS: Type and version of your operating system (incl. Windows, if running) Base memory: Total (usually 640k), free DOS memory below 640k with maximum +free block size, and free UMB size (if any) XMS: free XMS memory (if HIMEM or another XMS manager is loaded) EMS: LIM version, total and free memory (if EMM386 or other EMM loaded) Mouse: MS Mouse driver version, number of buttons, mouse type (serial, 0bus, PS/2), and Logitech version, if applicable. Floppies: Drive letter and size of each floppy drive. Hard Drives: sizes of (BIOS-accessible) hard drives (in MB), and all drive *letters for partitions of the hard drives. CD-ROM: drive letter(s) of CD-ROM drive(s) (if any); MSCDEX version Cache: type and (for some types) version and size of the disk cache (if Compression: type and (for some types) version of a online disk compress- (ion program (like DoubleSpace, Stacker). IFor further explanations, please refer to the corresponding detailed list accessible through the menu. JIf you don't want this overview page to be shown automatically at start-up6 K(or if it even crashes), you can prevent this in the Options dialog, in the IINI file, or by pressing and holding a Shift key after initialization has completed. See also: main menu Hardware/System 8In this submenu, you can select information pages about: your processor (if available:) what the CPUID command tells, and Pentium-specific stuff your Board and ROM BIOS and assorted info (if available:) the PCI devices in your system (if available:) Plug and Play the speed of the processor and the memory interface the parallel, serial, and game ports available on your system your graphics card your sound card VESA BIOS Extensions, if installed the interrupt vectors the BIOS data segment at segment 0040h the Interrupt ReQuest (IRQ) assignments the I/O Port Addresses overview the detailed contents and a table of the CMOS RAM See also: Operating system Memory Software Drives Configuration Files main menu Operating System 8In this submenu, you can select information pages about: type and version of the operating system, including information about MS- !Windows if it's currently running country-specific settings environment variables some DOS system variables the system file table(s) (SFTs) the installed devices (device drivers) other settings like BREAK/VERIFY and code pages *If Windows (386 enhanced mode) is running: * version and flags (as told by Windows) * system parameters * resources, memory * tasks, modules * paging file (swap file)4 from the Windows Old Application support module WinOldAp: GDI capabilities contents of the Windows clipboard a list of known virtual device drivers (VxDs) that have an API * SHELL 3* These items require that agSI\WinServ is running. See also: Hardware/System Memory Software Drives Configuration Files main menu Memory 8In this submenu, you can select information pages about: the DOS memory with active programs the XMS memory, if installed the EMS memory, if installed a memory manager with IOCTL interface support, if installed Microsoft's EMM386.EXE, if installed Novell's EMM386.EXE, if installed Quarterdeck's QEMM386, if installed Helix Software's RM386 / Micronics MICEMM, if installed an overview with the memory map possible RAM/ROM extensions speed comparisons of regions of your memory Also: a memory dump window where you can browse through your system's memory See also: Hardware/System Operating system Software Drives Configuration Files main menu Software LIn this submenu, you can select information pages about several programs and services: #In the menu, with more information: Mouse driver Network AMIS (Alternate Multiplex Interrupt Specification) APM (Advanced Power Management) APPEND ASSIGN COMM_DRV FOSSIL HyperWare products KEYB PrScr (ag) Rahmen (ag) SETVER SHARE TaskMax TBScanX VDS (Virtual DMA Specification) J"Others" shows a list with other installed programs with no additional in- .formation (only the version for some of them). See also: Hardware/System Operating system Memory Drives Configuration Files main menu Drives 8In this submenu, you can select information pages about: an overview of your logical drives (i.e. A: to ...) a sub menu for each available logical drive an overview of your physical drives (hard disks) a sub menu for each available hard disk a sub menu about IDE (ATA/ATAPI) devices a sub menu about SCSI devices, if an ASPI driver is installed an installed disk cache an active online compressor MSCDEX, the Microsoft CD-ROM Extensions, if installed See also: Hardware/System Operating system Memory Software Configuration Files main menu Configuration Files EIn this submenu, you can view several configuration files on drive C: CONFIG.SYS, CONFIG.DOS, CONFIG.W40 DCONFIG.SYS (alternative name for DR-DOS/Novell DOS), CONFIG.PTS (PTS-DOS) AUTOEXEC.BAT, AUTOEXEC.DOS, AUTOEXEC.W40 MSDOS.SYS, MSDOS.W40 DBLSPACE.INI, DRVSPACE.INI WIN.INI, SYSTEM.INI in any first-level subdirectory, and WINSTART.BAT and DOSSTART.BAT. LIn the file views, several keywords are shown highlighted, and the lines are word-wrapped. INote: *.DOS appears under Windows 95 when Windows 95 is running, *.W40 if Iyou had Win95 boot the previous version of DOS; also, MSDOS.SYS (.W40) is Ka text file with boot configuration under Win95 it's a binary system file under previous DOS versions. See also: Hardware/System Operating system Memory Software main menu Processor LThis item shows information about the CPU built in your system, the math co- 7processor (FPU), the cache size, and some other things. See also: Processor info list Hardware/System LCPUID/Pentium (not always available) HIf you have newer Intel 486 processor or a Pentium (or another processor Hwhich supports the CPUID command, e.g. from UMC), this item displays the Iresults from the CPUID command, plus some Pentium-specific information if there is a Pentium. See also: CPUID/Pentium info list Hardware/System Speed 7This menu item performs some CPU and memory benchmarks. See also: Speed info list Hardware/System Board and BIOS LThis menu item shows some information about your board and ROM BIOS, such as (BIOS date, bus type, keyboard type, etc. See also: Board and BIOS info list Hardware/System KPCI Information (if available) LThis menu item shows information about the Peripheral Component Interconnect ?bus, i.e. the devices installed, if applicable for your system. INote: As this test is done solely via the BIOS (and requires an Intel PCI JBIOS "v2.0" or above, it may be that it is not detected if you have an old Asystem with PCI bus but without the proper BIOS [are there any?]. See also: PCI info list Hardware/System KPlug and Play (if available) JThis list shows information about Plug and Play on your system, either via FPnP ROM-BIOS, DOS/Windows (3.x) ConfigManager software, or Windows 95. See also: Plug and Play info list Hardware/System Parallel Ports ?This menu item lists your parallel (LPT) ports and their state. See also: Parallel ports info list Hardware/System Serial Ports =This menu item lists your serial (COM) ports and their state. See also: Serial ports info list Hardware/System Other Ports: Game Ports IThis menu item gives information about your game port(s) and joystick(s). See also: Other ports info list Hardware/System Graphic Cards HThis menu item gives information about the graphics card(s) installed in your system. See also: Graphics cards info list Hardware/System Sound Cards JThis menu item gives information about the sound card(s) installed in your system. See also: Sound cards info list Hardware/System LVESA BIOS Extensions (only available if installed) LThis menu item gives information the VBE's installed on your system. Detect- ed are: VESA SuperVGA BIOS VESA XGA BIOS VBE/Audio Interface VBE/Power Management See also: VESA BIOS Extensions info list Hardware/System Interrupt Vectors HThis menu item lists the 256 interrupt vectors and their current owners. See also: Interrupt vectors info list Hardware/System BIOS Data Segment JThis menu item lists interesting parts of the BIOS data segment at address 0040:0h. See also: BIOS data segment info list Hardware/System IRQ Assignments AThis menu item lists the usage of the 16 Interrupt ReQuest lines. See also: IRQ assignment info list Hardware/System I/O Port Addresses FThis menu item shows the use (contents) of the I/O port address space. -***NOT YET IMPLEMENTED because it isn't safe! See also: I/O addresses info list Hardware/System CMOS RAM: Details JThis menu item lists interesting parts of the contents of your CMOS RAM in a detailed list. See also: CMOS RAM Details info list CMOS RAM Table Hardware/System CMOS RAM: Table >This menu item lists the contents of your CMOS RAM in a table. See also: CMOS RAM Table info list CMOS RAM Details Hardware/System CPUID and Pentium Information JThe CPUID command (Opcode 0Fh A2h) is a command new to Intel's Pentium and Lnewer i486 chips (also on some clones); if it's available, the following in- formation is displayed: CPUID: the 12-character manufacturer string: "GenuineIntel" for Intel, "UMC UMC UMC " for UMC, )"AuthenticAMD" for AMD, A"NexGenDriven" for NexGen, and only for the newer CPUs )"CyrixInstead" for (guessed it?) Cyrix. For Intel CPUs: Family: 4=486, 5=Pentium; 6=Pentium Pro (codenamed P6) Model: for 486: 1=DX, 2=SX, 3=DX2, 4=SL, 5=SX2, 7=DX2-WB, 8=DX4; others=? (The FDIV bug free steppings are 5=C1 and 4=B5, respectively.) GFor the Pentium Pro, the sA0 stepping is logically equivalent to the C0 3stepping, but on a different manufacturing process. Type (for P54C): one of original OEM processor (0) OverDrive processor (1) dual processor (2) reserved (3) For NexGen CPUs: Nx586-100: F/M/S=5/0/4, -120: 5/0/6 0For other CPU brands, it's similar to the above. If it's a Pentium, also displayed is whether the FDIV bug (where certain- Dstructured floating-point divisions have a wrong result) which was Hknown to Intel since summer 1994 but came to the public in December is5 Gpresent on this CPU, by checking if the operation x-(x/y)*y is zero for" Gthe double-precision variables x=8391667 and y=1572863 (as published in Ithe c't magazine 1/95). See above for the steppings of the corrected ver- sion. The value of the Time Stamp Counter (if available; a 64-bit value) tells :the number of clock cycles since power-on (or cold reset). JMay cause hang-ups or errors under certain conditions and is thus not dis- Gplayed under Novell DOS in V86 mode where this has happened (due to its GEMM386, obviously); also, Windows doesn't allow the RDTSC or RDMSR com- Gmands to be executed, and it may depend on the EMM386 version under MS-3 ;DOS. If it hangs in your configuration, you may disable it. Pentium Pro Processor Configuration (cache characteristics) ICalling CPUID with EAX=2 results in an array of byte descriptors with the 2following meanings (all with bit7=0; =1 reserved): 00h null 01h instruction TLB, 4K pages, 4-way set associative, 64 entries 02h instruction TLB, 4M pages, 4-way set associative, 4 entries 03h data TLB, 4K pages, 4-way set associative, 64 entries 04h data TLB, 4M pages, 4-way set associative, 8 entries 06h instruction cache, 8K, 4-way set associative, 32 byte line size 0Ah data cache, 8K, 2-way set associative, 32 byte line size 41h unified cache, 32 byte cache line, 4-way set associative, 128K 42h unified cache, 32 byte cache line, 4-way set associative, 256K 43h unified cache, 32 byte cache line, 4-way set associative, 512K J(41-43h are the Level 2 cache which is integrated in the Pentium Pro chip) !(TLB=Transition Lookaside Buffer) Pentium Pro BIOS Update: GThe Pentium Pro BIOS update allows the system BIOS or other software to Ginstall a microcode patch into the Pentium Pro processor. If available, displayed are: signature: should be 'INTELPEP' BIOS update loader version (32-bit hex number what does it mean?) number of 2K update blocks which can be recorded in NVRAM EThis function is available only in Real Mode (not in Virtual86 Mode). Capabilities Flags: a 32-bit value (the low 16 of which are displayed) states (see Speed); tell me if it's incorrect on your machine. JIf the CPU has a CPUID command available (see below), the "CPU" line shows 6its results, ignoring the information described above. IThe Virtual 8086 Mode is a mode where a complete 8086 1 MB environment is Fsimulated to DOS and the application, which is set by all multitaskers I(which take control over the system, above DOS), for example, Windows, or 1OS/2), and many memory managers, like EMM386.EXE. JThe CPUID command (Opcode 0Fh A2h) is a command new to Intel's Pentium and 'newer i486 chips (also on some clones). HThe FPU (Floating Point Unit) is an additional chip containing floating- Fpoint arithmetical operations (as opposed to the CPU with only integer Jarithmetics), (an 8087 for an 8086, an 80287 for an 80286, an 80387 for an I80386, or an i487 for an i486SX) or comes built-in in the CPU (486DX/DX2, K586 oops, I mean the "Pentium"). However, there are several manufacturers Lof (almost) compatible x87's between which the detection routine should also distinguish. JThe detection routines are taken from Norbert Juffa's CompTest, except the8 JCPUID command information about which was found in the c't magazine, issue 11/94. Board and BIOS BIOS Manufacturer: This tells the (suposed) manufacturer of your ROM BIOS, Gi.e. either IBM, AMI (American Megatrends, Inc.), AMI WinBIOS, Phoenix, 1Award, Dell, Hewlett-Packard, Compaq, or Toshiba. IFor AMI BIOSes, there also is the copyright string and for the newer ones also the version/revision. BIOS ID: (AMI BIOS only) The ID string (of an AMI BIOS only), which is Fdisplayed at the bottom line at startup, plus the other two lines dis- ?played in certain conditions (Ins key pressed during reset(?)). An interpretation can be found in the sub-window. more BIOS Date: This tells the date your system's ROM BIOS is from, in the way Git is (literally) stated at the end of the BIOS address space (at F000: FFF5h), e.g. 01/01/93. If an AMI PCI/Flash BIOS is in your system, there are (some of) the foll- !owing additional items displayed: CPU speed (low or high) Subsystem information: at present, only the names of the subsystems that are present are listed: recovery code system BIOS PCI configuration data logo data system BIOS/language CPU type (cf. below), showing also type/family/model/stepping (see also /CPUID info); and the clock frequency(?) in MHz. CPU-Type from BIOS and Mask revision: If the BIOS supports this function, Gthis tells the CPU type (386SL/SX/DX, Intel i376, RapidCAD, IBM 386SLC/ H486SLC, 486SX/DX/DX2/DX4, Pentium) and its mask revision, or a number if its name isn't known. HThis function is reported to be supported by "newer" IBM PS/2 models and "various" BIOSes. System Bus type: Tells the type of your system's bus, which is ISA, EISA, GMCA, MCA+ISA, or PCI bus (VESA Local Bus or other vendor-specific local busses are not detected). more PCI information EISA Configuration Utility (ECU) Version (EISA system only) EISA System Board ID: (EISA system only) The ID string of your system 7board, which consists of three letters and four digits. Intel Plug-and-Play BIOS: If found (signature $PnP in BIOS ROM), this Ftells version, real mode entry point and data segment of the PnP BIOS. FAlso checked is for the presence of the ACFG (Auto Configuration) BIOS B(via Int 1Ah), and the "VxD" DWCFGMG.SYS (for DOS+Windows 3.x) and :CONFIGMG (Windows 95; or device CONFIG$ under "MS-DOS 7"). Plug and Play BIOS32 Services: If present in your BIOS, this tells the address of the GService Directory header, the linear entry point and the version of the Gso-called BIOS32 Services which provide 32-bit protected mode access to HPCI and Plug-and-Play BIOS functions. The header is searched in the BIOS 1area starting at paragraph E000h (DWORD-aligned). Intel SMBus: If present and active in "Int 15h mode", this shows the ver- Jsion of the System Management Bus BIOS interface and the number of devices connected. IThe SMBus is a variant of ACCESS.bus being used by Intel and Duracell for Gthe Smart Battery proposal, but designed to be generic enough to handle other devices besides batteries. Multiprocessor Specification: If your BIOS supports this MP specifica- Htion, its revision (known: 1.1 and 1.4) is displayed along with the add- %ress of the MP structure in the BIOS. Model, Submodel, BIOS Revision: These tell the model and submodel number, Ias well as the BIOS revision (in hex) which is normally only used on an JIBM machine as the BIOS tells on an Int15/C0h call (or, if not supported on very old machines from address F000:FFFEh in the BIOS ROM). Table Feature Bytes: (only if supported) These are the feature bytes as told by Jthe BIOS Int 15/C0h call which give some configuration information in com- Hpact form (single bits each, numbered from right (b0) to left (b7), item present if bit is set (1)). description of the feature bytes JThere are also feature bytes 4 and 5, but they are either not used yet, or 4used only on some IBM machines in a yet unknown way. Keyboard type: The type of your keyboard (if supported by the BIOS), which His either a 122-, 101/102-key, or an old PC/XT/AT style 84-key keyboard. H(Note: "101/102-key" includes the keyboards designed for Windows 95 like Fthe Microsoft Natural Keyboard which have 105 keys (two "Windows keys" and an "Application key").) Base memory: Tells how much base memory is installed (in k-bytes, normally (and as maximum) 640k). more Extended memory: This is the amount of memory above 1meg (1024k) reported Hby Int15/88h that can be used directly as normal extended memory (not as EXMS or EMS memory; normally zero if such a memory manager is loaded). more A20 Gate: If supported by your BIOS (later PS/2, AMI PCI BIOS, Qualitas' I386MAX v6), this tells the state of address line 20 which is used for ac- Icessing the HMA, i.e. the 65520 bytes directly above 1 MB. Also stated is how it may be switched: using the keyboard controller and/or using bit 1 on I/O port 92h (PS/2 system control port A) Iand whether additional data is available (which position is yet unknown). See also: Hardware/System More on Bus Type 2These are the bus types and how they are detected: ISA, Industry Standard Architecture: The original 16-bit AT bus which Ievolved from IBM's PC/AT systems; it is assumed that you are using an ISA )bus if none of the below can be detected. MCA, Micro Channel Architecture: A faster and wider (32-bit) bus, plan- Kned as successor to the ISA bus and built in IBM's PS/2 systems, but failed Ksuccess in clone systems, mainly because MCA is incompatible with ISA cards I(different slots and specs); there may be some machines with both ISA and0 JMCA slots. Detection is done with the system's feature bytes, No.1, bits 1 and 0. EISA, Extended ISA: A 32-bit extension to the ISA bus offering more flex- Kibility, though allowing ISA cards to be plugged in EISA slots, too; it was Ldeveloped as opposition to MCA, but was a little expensive in the beginning. IDetection: ISA offers only port addresses up to 03FF, EISA up to FFFF; if Lthe bytes read from 0C80 (EISA system board ID register) and 0080 (DMA extra Lpage register, addressed also instead of 0C80 on ISA systems) are different, this should be an EISA system. Other bus types and extensions: VLB, VESA Local Bus: An addition (which defines an additional slot be- Khind the original ISA and EISA slots) which allows access at CPU speed, not Ljust at 8 to 8.33 MHz like (E)ISA, and at 32-bit bandwith (VLB-2 at 64-bit); Ihowever, the number of local bus units (as slots or on the main board) is Hlimited to 2-3 due to electrical reasons. VLB evolved as standard out of Lmany proprietary local bus specifications by system and board manufacturers. JVLB IS NOT DETECTED BY agSI [because I don't know how, if possible at all; (maybe only by detecting known chipsets]. PCI, Peripheral Component Interconnect: A bus designed by Intel which Ioffers 32-bit or 64-bit access at CPU speed (with the same limitations as FVLB, and with a new connector instead of (E)ISA compatible slots); PCI Hoffers somewhat more speed and more flexibility, but might be a bit more Kexpensive than VLB. Detection is done by a call to the Intel PCI BIOS v2.0c Hor above, Int1A/AX=$B101, and the PCI interface level is also displayed. See also: PCI Info %Model, Submodel, BIOS Revision Table Model Subm. System FFh FEh PC XT / Portable FDh PC junior 'FCh ... PC AT, early PS/2, clones FBh 00h newer PC XT "FAh 00h early PS/2, Model 30 F9h 00h PC Convertible F8h ... PS/2 possibly others BFor a more extensive list, see the Interrupt List (Int15h/AH=C0h). More on Base and Extended Memory GBase memory is the memory below 640k; normally, on machines used today, Ithis will be the maximum 640k. (This does not affect how much memory DOS, ?e.g. with 5+'s EMM386.EXE, QEMM or 386MAX, can use for itself.) IExtended memory: This is the memory above 1meg (1024k) reported by Int15/ J88h that can be used as normal extended memory, e.g. by older ram-disks or Kchaches, and is (should be) hooked by those programs in order to tell other Kprograms that only a reduced amount of extended memory is available; if you Ghave a memory manager installed like HIMEM.SYS you normally get the Jvalue 0k here, because this manager makes the extended memory available to0 4850h) Video7, size, DRAM/VRAM (Int 10h/6F00h => 5637h)% UltraVision Extensions, version (Int 10h/CC00h => ABCDh) Trident, date, size (Int 10h/1200h/11h)! Cirrus Logic, version, size (Int 10h/1200h/81h)& Chips & Technologies (C&T), size (Int 10h/5F00h => 5Fh) Realtek RTVGA (Int 10h/5F00h => 00h) Diamond Stealth 24 (Int 10h/7F00h/4000h => 007Fh) Diamond cards (?) with " " at C000h:0043h: displayed is the following +string [o.k. for my new Diamond Stealth 64] See also: Hardware/System LThe primary/secondary video system detection routine was taken from the book J'PC Intern 3.0', the video system detection from VGADOC4, the other infor- (mation is taken from the Interrupt List. Sound Cards /The following sound cards are detected by agSI: Ad Lib (or compatible), plus standard port address 388h driver version, interrupt (65h), and address (if installed) Sound Blaster (or compatible), plus port address (hex) interrupt (IRQ) (a '?' indicates it couldn't be detected) DSP (Digital Sound Processor) version %(1.00-2.00 for SB 1.0, 1.5, 1.6, MCV; 2.01 for SB 2.0, 3.01-3.xx for SBPro 2.x-?, 4.xx for SB 16, ?.?? for SB/SBPro ???) SBFMDRV FM-driver, version, interrupt (80h-BFh), address (if installed) Mixer settings (if DSP version 2)... ...which may be changed Roland MPU-401 MIDI interface Gravis UltraSound, plus port address memory MediaVision ProAudio Spectrum Driver MVSOUND.SYS version DMA channel IRQ number status string path to executable MVPROAS.EXE, if available Also displayed is the... BLASTER environment variable for SoundBlaster (compatible) cards, if present: A = base address (hex) I = interrupt request line (IRQ) D = 8bit DMA channel H = 16bit DMA channel (if 16bit transfers supported by sound card; if 9equal to 8bit channel, 16bit transfers are done via this) M = base address (hex) for the mixer P = MIDI port T = type identification of the card: 1 = SB 1.0/1.5 2 = SB Pro (2) 3 = SB 2.0 4 = SB Pro 3 6 = SB 16 others = ??? LNote that under Windows (386 mode), there will (sometimes?) no sound card be Jdetected as you normally don't have access to it if it is used by Windows. KAlso there can be a Windows message box stating that no sound can be played +the first time this info page is requested. KIf you really have none of the above [d'you live behind the moon?!?], there %will be only one line saying just so. See also: Hardware/System VESA BIOS Extensions (VBE) IThis displays the presence of any of the below-mentioned VBEs, defined by ,the Video Electronics Standards Association: VESA SuperVGA BIOS HThe VESA SVGA BIOS is a standardized extension to a SuperVGA card's BIOS I(as TSR program or integrated in the ROM) allowing standardized access to *video modes beyond the standard VGA modes. Displayed are: the signature (four characters, should be "VESA") the version of the VESA specification (known are 1.0, 1.1, 1.2, 2.0)) the name of the card's/chip's/BIOS's OEM the four capabilities bytes; used are: b0: DAC can be switched to 8-bit mode (instead of standard 6-bit mode for VGA palette modes) b1: =1 if non-VGA-compatible controller (VBE2 only?) b2: =1 if RAMDAC should only be programmed during vertical retrace to avoid flicker (VBE2 only?) the total amount of video memory BThese four items are for specification version 2.0 and above only: the OEM software version the vendor name the product name the product revision 5Then comes a list of the supported modes, listed with the mode number (hex) type of the mode: M=monochrome / C=color, T=text / G=graphics resolution: horizontal x vertical x colors (the latter only for graphics modes) JIf the resolution is displayed in parantheses, the call to get the resolu- Jtion info is not supported by your VESA driver/BIOS, and the resolution is taken from the knwon mode list. known VESA video modes, and note about the S3 modes ) Note: Some old cards with S3 chip and VESA included in the VGA BIOS do, Lalthough they report VESA version 1.00, not supply the video memory field of the returned information. VESA XGA BIOS Extensions KThis is a VBE similar to the SVGA BIOS, but for XGA-compatible cards. There4 10Dh 320x200x32K 112h 640x480x16M 117h 1024x768x64K >10Eh 320x200x64K 113h 800x600x32K 118h 1024x768x16M ?10Fh 320x200x16M 114h 800x600x64K 119h 1280x1024x32K ?110h 640x480x32K 115h 800x600x16M 11Ah 1280x1024x64K ?111h 640x480x64K 116h 1024x768x32K 11Bh 1280x1024x16M S3 OEM video modes: =201h 640x480x256 206h 1280x960x16 211h 640x480x64K =202h 800x600x16 207h 1152x864x256 212h 640x480x16M *203h 800x600x256 208h 1280x1024x16 *204h 1024x768x16 =205h 1024x768x256 20Ah 1152x864x64K 301h 640x480x32K = Diamond Stealth 64) J(Resolution is in Width x Height x Colors; 32K=32768, 64K=65536 (HiColor), "16M=16777216 (TrueColor), or Text) KNote: S3-specific modes follow in a second list after the end of the origi- Gnal list queried by the appropriate call, and this list may repeat some modes from the original one. VBE/AI: WAVE Device Feature Bits Bit(s) Description 0 8000hz Mono Playback 1 8000hz Mono Record 2 8000hz Stereo Record 3 8000hz Stereo Playback &4 8000hz Full Duplex Play/Record 5 11025hz Mono Playback 6 11025hz Mono Record 7 11025hz Stereo Record 8 11025hz Stereo Playback '9 11025hz Full Duplex Play/Record 10 22050hz Mono Playback 11 22050hz Mono Record 12 22050hz Stereo Record 13 22050hz Stereo Playback '14 22050hz Full Duplex Play/Record 15 44100hz Mono Playback 16 44100hz Mono Record 17 44100hz Stereo Record 18 44100hz Stereo Playback '19 44100hz Full Duplex Play/Record 20-26 reserved '27 driver must pre handle the data '28 Variable Sample mono playback '29 Variable Sample stereo playback %30 Variable Sample mono record %31 Variable Sample stereo record VBE/AI: MIDI Device Feature Bits Bit(s) Description 10-3 reserved for GM (General MIDI) extensions !4 Transmitter/Receiver only 5 Patches preloaded #6 MIDI receive has time stamp -8 MIDI interrupt driven input supported #9 MIDI polled input supported %10 MIDI remote patches supported others reserved "VBE/AI: VOLUME Device Feature Bits Bit(s) Description '0 Stereo Volume control available $2 Low Pass Filter is available %3 High Pass Filter is available ,4 Parametric Tone Control is available 5 selectable output paths +8 Azimuth Field positioning supported '9 Phi Field positioning supported 31 Master Volume device others reserved Interrupt Vectors LThis lists the addresses of the interrupt handlers for the 256 system inter-9 Jrupts, their owners and their usual usage. An asterisk "*" after the owner Lindicates there's an immediate IRET instruction at the interrupt handler, so Ithis call does absolutely nothing. (However, there are several interrupts Lthe handlers of which (e.g. in the BIOS) do some internal stuff, but nothing Kelse; you may see that from the display of the same address for several in- terrupts.) 0Groups of exactly equal interrupts are combined. If use of protected mode is not disabled (see Options dialog), and a DPMI Ihost is present, the sub-list will present a list of the (used) protected mode interrupt handlers. INote that, if using UMBs, some regions like the VGA BIOS will be reported Jas "DOS" (because that's how DOS excludes these regions from memory alloc- Jation: by defining an MCB around them); if not using UMB, the upper memory !regions may be called "ROM BIOS". INote also that the last few interrupts contain some data (???) and do not point at reasonable stuff. See also: Interrupt Overview Hardware/System BIOS Data Segment HThe BIOS data segment at 0040h holds many items of information, the most Hinteresting (and useful) of which are listed in the info window. I don't Ilist all the items here in the help because there is no need to duplicate Jthe file MEMORY.LST with an excellent list of the BIOS segment 0040h which &comes as a part of the Interrupt List. See also: Hardware/System IRQ Assignments JThis lists the assignment of the hardware IRQ (Interrupt ReQuest) channels K(controlled by a chip called "8259"), which are 8 on old PC/XT compatibles, and 16 on an AT style computer. JDisplayed are the status (used or free), and standard assignments (some of Jwhich are just default settings which may be changed). Note that some IRQs Imay be reported as used only when they are really used at the moment, for instance, a sound card's IRQ. See also: Hardware/System I/O Port Addresses -***NOT YET IMPLEMENTED because it isn't safe! See also: Hardware/System CMOS RAM KThe CMOS ("Complementary Metal Oxyde Semiconductor") RAM is a battery-back- Hed, small memory area (outside the normal RAM) where the real-time clock 5data is stored, as well as configuration information. KThis info list tells you the size of your system's main CMOS RAM (64 or 128 Ibytes accessible via Port 70h/71h; additional (e.g. EISA) CMOS RAM is not0 >detected), and some (more or less) interesting detailed items. 6Detailed items are displayed for the following BIOSes: AMI Hi-Flex BIOS (386 and above, dated 07/07/91 and newer (?)), AMI WinBIOS (newer, mostly in Flash-ROM), AWARD (only for "Modular BIOS 4.50G" ?), Phoenix (maybe only older versions), IBM PS/2. @(Neccessary is, of course, that they could be detected; see also Board and BIOS.) GSelect CMOS RAM table for a complete tabular list of the CMOS values. JYou may change date and time by selecting one of the first two data lines. See also: Hardware/System CMOS RAM Table EThis gives you an overview about the 64 or 128 bytes of the CMOS RAM. .Select CMOS RAM Details for a detailed list. See also: Hardware/System CMOS Details IHere is some additional information on the detailed CMOS items. Note that #some are different on some systems. 0A: Status Register A (read/write) (usually 26h) bit7: 1=time update cycle in progress, data ouputs undefined bit6-4: 22 stage divider. 010b = 32.768 Khz time base (default) bit3-0: Rate selection bits for interrupt: 0000b none "0011b 122 microseconds (minimum) 1111b 500 milliseconds &0110b 976.562 microseconds (default) 0B: Status Register B (read/write) bit7: 1 enables cycle update, 0 disables bit6: 1 enables periodic interrupt bit5: 1 enables alarm interrupt bit4: 1 enables update-ended interrupt bit3: 1 enables square wave output bit2: Data Mode: 0: BCD, 1: Binary bit1: 24/12 hour selection: 1 enables 24 hour mode bit0: US Daylight Savings Enable: 1 enables 0C: Status Register C (read only) bit7: Interrupt request flag - ;1 when any or all of bits 6-4 are 1 and appropriate enables (Register B) are set to 1. Generates IRQ 8 when triggered. bit6: Periodic Interrupt flag bit5: Alarm Interrupt flag bit4: Update-Ended Interrupt Flag bit3-0: ??? 0D: Status Register D (read only) bit7: Valid RAM: 1 indicates battery power good, 0 if dead or disconnected. bit6-0: ??? 0E: Diagnostic Status Byte (should be zero) bit7: 1: clock has lost power bit6: 1: incorrect checksum bit5: 1: equipment configuration is incorrect; power-on check requires %that at least one floppy be installed bit4: 1: error in memory size bit3: 1: controller or disk drive failed initialization bit2: 1: time is invalid bit1: 1: installed adaptors do not match configuration bit0: 1: time-out occured while reading adaptor ID 0F: Reset Code (IBM PS/2 "Shutdown Status Byte") normally zero For all the other registers please refer to some specific documentation Hwhich I regret I can't include here due to its complexity; for instance, Hyour system's manual, the manufacturer, or some utilities or informative Jfiles that go around on BBSs, CompuServe, Internet, etc., like Padgett Pe-1 Lterson's file CMOS.LST included in Ralf Brown's Interrupt List, or for AMI JBIOSes the AMISETUP utility (shareware) by Robert Muchsel from Konstanz, Germany. See also: Hardware/System !Operating System Type and Version HThis item shows information about the currently running operating system (DOS, DOS+Windows, OS/2). See also: Type and Version info list Operating System Country-Specific Settings HThis item shows information about the current country setting, like code page, date/time format, etc. See also: Country info list Operating System Environment Variables This item shows the contents of the SFTs, i.e. all open files. See also: System File Tables info list Operating System Devices / Device Drivers KThis item lists the installed device drivers (block and character devices). See also: Device Drivers info list Operating System Other Settings KThis item displays some other settings like the BREAK/VERIFY flags and code pages. See also: Other Settings info list Operating System Windows: KThis item is just a headline for the following item(s) when Windows is run- ning. See also: Version and Flags WinOldAp GDI WinOldAp Clipboard Virtual Device Drivers Paging File System parameters Resources SHELL module Operating System Version und Flags JThis item shows what Windows tells as Windows and DOS versions, as well as the Windows flags and directory. .This item requires agSI\WinServ to be running. See also: Version and Flags info list Operating System WinOldAp GDI Capabilities KThis item displays the capabilities of the Graphic Device Interface of Win- 9dows (accessible through the WinOldAp module of Windows). See also: WinOldAp GDI info list WinOldAp Clipboard Operating System WinOldAp Clipboard JThis item displays a list of the current contents of the Windows clipboard 4(accessible through the WinOldAp module of Windows). See also: WinOldAp Clipboard info list WinOldAp GDI Operating System Virtual Device Drivers (VxDs) @This item lists the installed VxDs in Windows 386 enhanced mode. See also: VxDs info list Operating System Paging File (Swap File) KThis item shows information about Windows' swap file (if paging is active). .This item requires agSI\WinServ to be running. See also: Paging file info list Operating System SHELL (Windows Module) >This item shows information about the SHELL module of Windows. .This item requires agSI\WinServ to be running. See also: SHELL info list Operating System Resources, Memory LThis item shows the amount of free space of Windows' global heap memory, the Cnumber of items on it, and the three resources (system, GDI, user). .This item requires agSI\WinServ to be running. See also: Resources, Memory info list Operating System Tasks, Modules @This item shows the active Windows tasks and the loaded modules. .This item requires agSI\WinServ to be running. See also: Tasks, Modules info list Operating System Windows System Parameters JThis item shows some of Windows' system parameters, like mouse speed, icon spacing, etc. .This item requires agSI\WinServ to be running. See also: System parameters info list Operating System !Operating System Type and Version Reported DOS version: This tells the version of DOS via an Int21/30h call, Fjust like a VER command would return it. With some simple utilities or Jwith SETVER.EXE (MS-DOS 5.0 and above), this version may be changed (which Jmay be useful to run programs that test the version via the above call and Jneed a specific version). Other operating systems may return other values like 20.00 in OS/2 2.0. True OS version: This 'sees through' SETVER or similar stuff and tells the Gtrue version; however, it is also reported by the OS (Int21/3306h), but Hnormally not changed by an utility. If the "true" version is 3.31, it is Jalso checked if this is Digital Research's DR-DOS or Novell DOS 7 (via the Eundocumented call Int21/4452h; DR-DOS 5.1, for display space reasons, Jmeans DR Multiuser DOS 5.1; 6.01 means the DR-DOS 6.0 March 1993 "business Fupdate", 7.0 is Novell DOS 7.0 which reports true version 6.00 (DR was bought by Novell)). AWindows NT reports "5.50", according to R.Brown's Interrupt List. HIf you see a '?' in this field, the Int21/3306h call is not supported by $your OS version, e.g. under DOS 3.3. Revision: This field displays the revision number of your operating sys- Htem, if it exists (i.e. reported by the 3306h function) it is normally H0, but under OS/2 it tells the Internal Revision, e.g. for the re- Jvision 8.152 of the 2.99 Warp II beta version from August 1994; also, PTS- DOS seems to use this field. OEM byte: This byte (in hex) tells the Original Equipment Manufacturer I(OEM) of the OS (or its machine-specific version). If known, the OEM will also be displayed litterally. List of OEM bytes Serial number: This 24-bit value tells the (user) serial number; it is not &used by most systems (except PTS-DOS). in HMA? and free HMA space: This states whether DOS is resident in the High Memory HArea (HMA); if yes, the amount of free HMA space (in bytes) is also dis- played. DThe High Memory Area (only available on 80286+ systems, normally al- Ilocated using an XMS driver such as HIMEM.SYS) is the last in the proces- Hsor's Real Mode accessible segment, FFFFh, and its size is exactly 65520 Gbytes (segment size 64k=65536 minus the last 16 bytes of the 1-Megabyte Iaddress space). Under DOS 5.0+, you may tell DOS to use it for itself and Gfree up some memory in the lower area (0-640k area), using the DOS=HIGH Fstatement in your CONFIG.SYS, which requires HIMEM.SYS (or another XMS driver) installed. in ROM? Only displayed when DOS (5.0 and above) actually is in ROM (mainly on notebook computers). Windows version Windows mode Virtual Machine ID: These fields tell the version and mode (real/standard Gor enhanced) of Windows if you are currently running Windows; it is not Idisplayed if not. Also displayed is the Virtual Machine ID word (the num- Jber of the DOS box in Windows enhanced mode; Windows itself runs in VM 1). JNote: What Microsoft decided to call "Windows 95" reports consequently version 4.0. Windows95 swap file name and size (in KB) pager type (none, through MS-DOS, protected mode I/O) Linux DOS Emulator: If you are running agSI inside the Linux DOSEMU, this +line tells its version and patchlevel (pl).@ JNote: As DOSEMU uses Interrupt E6h, the system may hang when agSI calls it F(outside Linux) when the address of the interrupt is messed up by some Fprogram (IBM's anachronistic BASICA may be a candidate, but maybe also? Gsome ROM BIOS) which doesn't point to an interrupt handler; disable the =DOSEMU test then with a line "Disable=OOSL" in your INI file. See also: Operating System !List of known DOS OEM byte values 00h: IBM / Digital Research/Novell 01h: Compaq 02h: MS Packaged Product 04h: AT&T 05h: ZDS (Zenith Electronics) 06h: Hewlett-Packard 07h: ZDS (Groupe Bull) 0Dh: Packard-Bell 16h: DEC 23h: Olivetti 28h: Texas Instruments 29h: Toshiba 4Dh: Hewlett-Packard 66h: PhysTechSoft (PTS-DOS) 99h: General Software's Embedded DOS 99h: STARLITE architecture (OEM DOS, NETWORK DOS, SMP DOS) EEh: DR-DOS (?) EFh: Novell DOS (?) FFh: Microsoft, Phoenix D(If you are using an OEM version I do not yet know, please tell me.) Country Settings Country Code: The current country setting which is normally the one spec- Fified in your CONFIG.SYS (with COUNTRY=...). This number [displayed in Jthree digits with leading zero it looks better this way, I think] is the Gsame as the country's telephone number, e.g. for the U.S., Germany, etc. Date Format that is used on your system, which is one out of Month - Day - Year (in the USA) Day - Month - Year (in Europe) Year - Month - Day (in Japan) Date Separator: The character used to separate the day's, month's, and )year's display, normally "/", "." or "-". Time Format (Hours): Tells whether the 12- or the 24-hour format is used. Time Separator: The character used to separate the hours', minutes', and Jseconds' display (you also see it in the upper right corner), normally "." or ":". Currency Name: The up-to-4-character name of the currency set on your sys- 1000s' and Decimal Separator: The characters that should be used [why do Fnot all programs check this?] to separate each three digits of a large Jnumber, and the decimals, respectively, for example "12,995.99", in Germa- ny "12.995,99". Digits after Decimal: How many digits are normally used to display the "small currency value (normally 2). Data/List Separator: The character used to separate a list (normally ",", or ";" in Germany). See also: Operating System Environment Variables KThis info list shows something about the so-called environment (of the cur- Krent process, i.e. AGSI.EXE, but normally indifferent from the master envi- ronment): Total environment size: This should be the maximum size of the (master) Aenvironment in bytes, but I don't know a reliable way to find it. Used environment size: How many bytes are actually used (by the variables, )the owner name, and maybe other strings). Environment variables: The number of the variables listed below. The list: Just like a SET command would show, this is the list of the en- Jvironment variables, in the order they are stored in the environment, plus Gits Owner (the full pathname of the program the environment belongs to, Hthat is AGSI.EXE), and maybe other strings (normally none) stored there. HNote that you cannot access lower-case variables the normal way (the SET Icommand, Turbo Pascal's GetEnv, etc.), for example, the "windir" variable Eset by Windows to its directory (C:\WINDOWS, or something like that). See also: Operating System DOS System Variables KThese are some of the values from DOS' "SYSVARS", the List of Lists , ret- Lrieved with an Int21/52h call, which contains many items; the most interest- ing are displayed here. @For a full documentation of the SYSVARS, see the Interrupt List. sharing retry count (word, offset -12h) sharing retry delay (word, offset -10h) segment of first memory control block (word, offset -2h) maximum bytes per sector of any block device (word,offset 10h) number of protected FCBs (the y in FCBS=x,y from CONFIG.SYS; 0 in DOS 5+, ,not valid (65535) in OS/2; word, offset 1Eh) number of block devices installed (26 in OS/2; byte, offset 20h) number of available drive letters (largest of 5, installed block devices, ,and CONFIG.SYS LASTDRIVE=; byte, offset 21h) number of JOIN'ed drives (byte, offset 34h) DOS 4 and above: the x in BUFFERS x,y ("0" under OS/2; rounded up to multiple of 30 if in EMS; word, offset 3Fh) number of lookahead buffers ("0" under OS/2; the y in BUFFERS x,y; word, offset 41h) boot drive (1=A:) (byte, offset 43h) use DWORD moves (flag=01h; 80386+), 00h otherwise (byte, offset 44h) extended memory size in K (not valid under OS/2 ?; word, offset 45h) some pointers: first Drive Parameter Block (dword, offset 00h) first System File Table (dword, offset 04h) active CLOCK$ device's header (dword, offset 08h) active CON device's header (dword, offset 0Ch) array of Current Directory Structures (dword, offset 16h) system FCB tables (dword, offset 1Ah) SETVER program list (dword, offset 37h, DOS 5+) "DR-DOS/Novell DOS System Variables KIf this DOS type is running, here are some DR-DOS specific variables from a list reported by Int21/4458h: history control structure for COMMAND.COM history (DDS=DOS Data Segment) history control structure for application history extended memory at startup (in KB) internal far jump entry points: number and address (segment) first free and used HMA memory block (if the DOS kernel is in the HMA) 5offset in HMA segment FFFFh; "0000" if not applicable full COUNTRY.SYS filename SHARE hook table (offset in DDS) See also: Operating System System File Tables 7(Not supported in an OS/2 2.x/3.x Virtual DOS Machine.) HHere displayed is the maximum number of open files (the FILES setting in LCONFIG.SYS, possibly more under Windows), the number of currently open files J(including the standard devices) and more detailed information about them, Jtaken from the System File Tables. There are usually two SFTs: one for the Dfirst five files/devices, one for the rest (CONFIG.SYS's FILES - 5). System File Table Address Files in this SFT; for each opened file: file/device name (in FCB format, i.e. without period, blank-padded) &AUX, CON, PRN are the standard devices handles for this file (at least 1; more for CON, PRN etc.) access mode: "FCB", if opened via the old File Control Block method either read only, write only, read/write, or redirected "inherit" if child processes (started via the EXEC function) inherit this file sharing mode: either of... compatible (old method used) DenyAll: disables all accesses by other processes DenyRead/Write: disables read/write accesses by other processes DenyNone: don't disable any other access ?: unknown mode attributes set: (for files only) (bit 7) sh=shareable (Novell NetWare) (bit 6) ? =unused (bit 5) A =archive (bit 4) D =directory (bit 3) V =volume label; execute-only (Novell NetWare) (bit 2) S =system (bit 1) H =hidden (bit 0) R =read-only drive: the drive the file is on (for files only) device info flags: some of the following: (bit 15) remote file (bit 14) do not set file date/time on closing (bit 13) named pipe (DOS 4+) (bit 12) no inherit on EXEC (bit 11) network spooler (DOS 4+) (bit 7) (set device, clear if file (only if local; DOS 4+)) character device: (bit 6) EOF on input (bit 5) raw (binary) mode (bit 4) device is special (uses INT 29) (bit 3) clock device (bit 2) NUL device (bit 1) standard output (bit 0) standard input disk file: (bit 6) file has not been written (bits 5-0: drive number) date and time of first opening (device) or creation (file) file size (in Bytes) current offset from start (device: characters read/written?) machine number in a network, Virtual Machine ID under Windows enhanced Cmode; Windows itself runs in VM 1, and there is no VM 0 (a VM ID 0, Ewhich is not displayed here, belongs to a file/device that was opened before the start of Windows). AFor the VM ID of this DOS session (if you are under Windows), see OS type and version. owner PSP segment (owner=file/device opener; AUX, CON, PRN: segment of HIO.SYS/IBMBIO.SYS startup code) plus the owner's name from the MCB which "should be directly before the PSP. Sharing Record address: if SHARE.EXE is loaded, and this field is non- !zero, some sharing info is shown: full pathname of the file checksum of the above name Record Lock Record address; if existing, for each lock: locked region (file offsets) SFT pointer PSP of owner of the lock lock type (lock all accesses or only write accesses) SFT address of this file, which is the address of this SFT unique sequence number GThese lines are not shown under Novell DOS 7 because its SHARE does not ;support these fields, or uses an (unknown) internal format. See also: Operating System Devices / Device Drivers KThis page displays a list of all devices (device drivers) installed on your Fsystem. Some are internal to DOS, others are loaded in CONFIG.SYS with DEVICE=. The information shown is: Device: The name of the driver, if given; a number in () means it is a Fblock device (like disk drives), and the number is the number of units inside of the device driver. Header: The address where the driver resides. Strategy: This is the address used to setup a call. Interrupt: The address called to execute a command. FAlso it is indicated by a * if these are protected mode routines (e.g. Cunder Windows (95) which may not even reflect This call back to V86 Fmode); this is the case if the byte at the entry point address is 63h, the opcode for the ARPL command. Attributes: There are 16 bits that define what the driver does. CNumbering left to right, with left being 15, plus one character for quick identification: 15: 1 = character device, 0 = block device 14: 1 if IOCTL (special commands) are supported 13: block device: 21 means to use the boot sector to get information, 0 to use media ID byte character device: #1 means output until busy supported- 12: block device: 1 means it is remote (network) char device: reserved (0) 11: 1 if open/close/removable media is supported 10: reserved (0) 09: reserved (0); block device: direct I/O not allowed??? $(set by DRIVER.SYS for "new" drives) 08: reserved (0); see bit 08B 07: 1 if generic IOCTL check call supported (driver command 19h)< 06: 1 if generic IOCTL call supported (driver command 13h) 05: reserved (0)" 04: 1 if the CON device, and fast output (Int 29h) supported 03: 1 if the CLOCK$ device 02: 1 if the NUL device 01: block device: 1 means 32-bit sector addressing supported. +char device: 1 means it is standard output! 00: 1 if device is standard input Some common driver names: AUX, CON, PRN: standard internal devices EMMXXXX0: an EMS driver XMMXXXX0: an XMS driver EMMQXXX0, $MMXXXX0 or &MMXXXX0: disabled EMS driver (no EMS at all, or 'under Windows 3 which supplies its own) SMARTAAR: Disk cache (older versions of SmartDrive) SETVERXX: SETVER.EXE See also: Operating System Other Settings BREAK: This tells the current state of the BREAK flag (it may be set using FBREAK ON or BREAK OFF from the command line). If BREAK is off, the key Icombination Ctrl+Break (or Ctrl+C) which you may interrupt a program with His only tested on text IO, thus the program may only be interrupted when .performing such tasks (via the DOS Int21 API). VERIFY: This tells the current state of the VERIFY flag (may be set like JBREAK from the command line); if set to ON, all normal disk and file oper- Hations (e.g. COPY), are verified by reading and comparing the file after the operation. Current / Default Codepage: This tells the currently selected, and the 'default codepage (selected on startup). IA codepage is a set of characters with different appearance. This is used Hmainly to support national language characters; for example, in codepage H850 (multi-lingual), there are more accented letters for several langua- Iges; if you use this, some frame characters (those containing both double Gand single lines) are not available. The codepage normally used is 437. CIf no additional codepage support is installed, this field says so. See also: Operating System Windows Version and Flags IThis page shows what Windows reports as it version, the Windows flags and directory. .This item requires agSI\WinServ to be running. "Displayed are the following items: Windows version (as Windows tells it to Windows programs; 3.10 also for 8Windows/WfW 3.11, and 3.95 for Windows 95 beta versions) DOS version Flags (a hex dword), with the following meanings: b00: Windows running in protected mode (always set in 3.1+) b01: CPU is a 286 b02: CPU is a 386 b03: CPU is a 486 or better b04: Windows running in 286 standard mode b05: Windows running in 386 enhanced mode b10: system has math coprocessor b11: Windows running with paged memory b12: (sometimes set under Windows 95: when not based on a complete DOS +configuration(?), which includes Safe Mode) b13: Windows 95 (?) other bits: meaning unknown Number of tasks Win32 System version and Win32s version: Win32 is the 32-bit system of FWindows NT, Win32s (s=subset) the support for functions callable under FWindows 3.1x and Windows 95. If not installed, these two lines are not Hdisplayed at all; otherwise, the Win32 system version should be 1.00 and Hthe Win32s version the version number of the implementation, for example 1.25. Windows directory and System directory: These tell the Windows base and system directories, )usually C:\WINDOWS and C:\WINDOWS\SYSTEM. See also: Operating System Windows WinOldAp Clipboard JWINOLDAP is MS Windows' interface for "old" (character-based) DOS applica- 9tions to have access to the clipboard and the GDI driver. HThe following clipboard data types are known; they are only displayed if Jthey are currently in the Windows clipboard. The size is obviously rounded up to a multiple of 32 bytes. (01h) text (02h) bitmap (03h) metafile picture (04h) SYLK (Symbolic Link) (05h) DIF (Data Interchange Format) (06h) TIFF (Tag Image File Format) (07h) OEM text (08h) DIB bitmap (0Ch) Wave Audio (80h) WRITE formatted text (81h) DSP text (82h) DSP bitmap LThere are other common types which are not accessible from DOS: Color palet- :te, Rich Text Format, Native, and OwnerLink, for instance. JYou may empty the clipboard by selecting (double-click/Ctrl-Enter) the ac- cording line. See also: WinOldAp GDI Operating System Windows WinOldAp GDI JWINOLDAP is MS Windows' interface for "old" (character-based) DOS applica- Jtions to have access to the clipboard and the GDI driver. Displayed in the ;menu is also the version of WinOldAp (2.00 in Windows 3.1). JThe following information about the GDI device driver and its capabilities 8is displayed (normally, this is just your video driver): (00h) driver version (the version of Windows the driver was made for) (02h) device classification: one of (00h) vector plotter (01h) raster display (02h) raster printer (03h) raster camera (04h) character-stream, PLP (05h) Metafile, VDM (06h) display-file (04h) width in mm (06h) height in mm (08h) width in pixels (0Ah) height in pixels (0Ch) bits per pixel (0Eh) number of bit planes (10h) number of brushes supported by device (12h) number of pens supported by device (14h) number of markers supported by device (16h) number of fonts supported by device (18h) number of colors (1Ah) size required for device descriptor (1Ch) curve capabilities: displayed is what is supported (bitfield): 0 - circles 1 - pie wedges 2 - chord arcs 3 - ellipses 4 - wide lines 5 - styled lines 6 - wide styled lines 7 - interiors (1Eh) line capabilities 0 - ??? 1 - polylines 2 - markers 3 - polymarkers 4-7 as above (20h) polygon capabilities 0 - polygons 1 - rectangles 2 - trapezoids 3 - scanlines 4-7 as above, for borders (22h) text capabilities 0 - output precision character 1 - output precision stroke 2 - clipping precision stroke 3 - 90-degree character rotation 4 - arbitrary character rotation 5 - independent X and Y scaling 6 - double-size 7 - integer scaling 8 - continuous scaling 9 - bold 10 - italic 11 - underline 12 - strikeout 13 - raster fonts 14 - vector fonts 15 - reserved (24h) clipping capabilities 00h = none, 01h = clipping to rectangles (26h) bitblt capabilities (BIT BLock Transfer) 0 - simple bitBLT 1 - device requires banding support 2 - device requires scaling support 3 - supports >64K bitmap GThose capabilities not supported by the driver have to be calculated by HWindows and split into single simple commands which then are sent to the driver. (28h) X aspect (2Ah) Y aspect (2Ch) length of hypotenuse of aspect (58h) logical pixels per inch of width (5Ah) logical pixels per inch of height See also: WinOldAp Clipboard Operating System Virtual Device Drivers LHere you see some of the VxD's of Windows 386 enhanced mode that are instal- Jled on your system and currently running; only those that have a real mode IAPI are (can be) shown. (The name "VxD" comes from "Virtual xxx Driver".) @The VxD API address is queried via the Int2Fh AX=1684h function.' 5For more about existing VxDs, see the Interrupt List. JFollowing is a list of the VxDs recognized by agSI; those denoted with a * Khave only a protected mode API and are not checked for if you have disabled 8using protected mode (see command line, Options dialog). VMM, ID 0001h Virtual Machine Manager VPICD, ID 0003h, version PIC=Programmable Interrupt Controller VTD, ID 0005h, version Timer displayed is: the time Windows is active the active time of this virtual machine *(where it actually had CPU time available) REBOOT, ID 0009h * Ctrl-Alt-Del handler VDD, ID 000Ah Virtual Display Device (GRABBER) displayed is the level of video virtualization: none, fully, or separ- Aately for text modes, single-plane and multi-plane graphics modes VMD, ID 000Ch, version Mouse VKD, ID 000Dh * Keyboard VCD, ID 000Eh * COMM VPD, ID 000Fh * Printer IOS, ID 0010h * DOS386 IOS Device (Windows95 version) VMCPD, ID 0011h Math CoProcessor DOSMGR, ID 0015h, version DOS Manager: DOS data instancing SHELL, ID 0017h, ver.? * SHELL (Windows module) VNETWARE, ID 001Ah Novell NetWare DOSNET replacement; DOSNET has no real-mode API VFD, ID 001Bh Floppy WINDEBUG, ID 001Dh * Debugger support (also TDDebug) PageFile, ID 0021h, ver.? * Paging File (Swap file) device VXDLDR, ID 0027h (Windows for Workgroups (WfW) 3.11) NDIS, ID 0028h (Network Driver Interface Spec.; WfW 3.11) VWIN32, ID 002Ah (Windows 95 Win32 interface) VCOMM, ID 002Bh (WfW 3.11) W32S, ID 002Dh, ver.? * Win32s MACH32, ID 0030h * ATI Mach32 video card SERVER, ID 0032h Int21 File Server (WfW 3.11) CONFIGMG, ID 0033h Configuration manager (Windows 95) VCMD/DWCFGMG,0034h, ver. * Plug-and-Play configuration manager number of identified devices; for more details, see the Hardware menu VFBACKUP, ID 0036h (Windows 95) VCOND, ID 0038h (Windows 95) VPMTD, ID 003Ah IFAX Scheduler Device (WfW 3.11) DSVXD, ID 003Bh DoubleSpace VxD from MS-DOS v6.x IFSMGR, ID 0040h Installable File System Manager VIPX, ID 0200h NetWare Virtual IPX Driver WINICE, ID 0202h SoftICE/W BCW, ID 0205h Nu-Mega Bounds Checker for Windows DPMS, ID 0207h Novell DOS Protected Mode Services VCOMMUTE, ID 0234h PC Tools Commute VNWD, ID 02DEh, version Novell DOS 7 VTDAPI, ID 0442h * MMSys Win386 VTAPI Device VSBD, ID 0445h Sound Blaster VADLIBD, ID 0446h AdLib mmdevldr, ID 044Ah MultiMedia Device Loader mssblst, ID 044Eh MS SoundBlaster VflatD, ID 045Dh, ver. * dva.386, part of Win32s UNIMODEM, ID 0460h * VNetSup, ID 0480h Virtual Net Support (WfW 3.11) VSHARE, ID 0483h, version Windows for Workgroups Virtual SHARE IFSMgr, ID 0484h Installable File System Manager (WfW 3.11) VFAT, ID 0486h Win386 HPFS Driver (WfW 3.11) VCACHE, ID 048Bh Virtual File Cache (WfW 3.11) RASMAC, ID 048Dh enhanced mode WfW RASMAC device VSWITCHD, ID 0750h to tell DOS apps if they are windowed the state of this DOS box is displayed VMB, ID 1021h Microsoft C/C++ 7.00 WXSRVR VPFD, ID 1022h Microsoft C/C++ 7.00 MMD, ID 1025h Microsoft C/C++ 8.00, Visual C/C++ 1.00 PIPE, ID 2020h by Thomas W. Olson, in Win/DOS DevJrn 5/92 VADLIBWD, ID 21EAh * Adlib Waveform Driver by John Ridges VFINTD, ID 2200h, version Norton VFINTD (Norton Desktop) VNSS, ID 24A0h * Norton Screen Saver (Norton Desktop) VNDWD, ID 24A1h Norton VNDWD Device (Norton Desktop) SYMEvent, ID 24A2h Norton Utilities v8 VILD, ID 2540h INTERLNK client from MS-DOS v6.x VASBID, ID 2640h * WinResKit: Artisoft Sounding Board Device FBW_VXD, ID 2760h, version FastBack for Windows COMMTASK, ID 2860h * Windows 386-mode preemptive tasker by James #A. Kenemuth of Interabang Computing PharLap, ID 28A1h PharLap 386|DOS-Extender DOSXNT.386 VXD, ID 28C0h Generic VxD for real and protected mode by $Andrew Schulman in MSJ February 1993 EDOS, ID 2925h Enhanced DOS by Firefly Software VSBPD, ID 292Dh Sound Blaster Pro VCAD, ID 304Ch Plug and Play Configuration Access WPS, ID 310Eh, ver. * MS DevNet CD-ROM: Windows Process Status LMOUSE, ID 318Ah Logitech Mouse VFRAD, ID 32CBh Dr.Franz - Simulatan's diagnotics VFRAD.386 POSTMSG, ID 4321h SIWVID, ID 7A5Fh Soft-ICE for Windows video driver VWFD, ID 7FE0h to tell DOS apps if they are (w)indowed or +(f)ull-screen; by Neil Sandlin of Microsoft VWATCHD, ID 7FE1h basic driver w/ no functionality except %tracing by Keith Jin of Microsoft PSS VFINTD, ID 7FE5h Virtual Floppy Interrupt trapper by Neil Sandlin of Microsoft VMPAGES, ID 7FE7h demonstration of exporting VxD services, by Neil Sandlin of Microsoft VPOSTD, ID 7FE8h PostMessage() demo by Curtis J. Palmer of MS See also: Operating System Windows System Parameters LThis page lists some of Windows' system parameters, most of which can be set in the control panel. .This item requires agSI\WinServ to be running. "Displayed are the following items: Error beep (on/off) window border size (in pixels) fast task switch (on/off) grid granularity icon title wrap (on/off) keyboard delay keyboard speed menu drop alignment (left/right) mouse threshold 1 mouse threshold 2 mouse speed screen saver active (yes/no) screen saver time-out (in seconds) horizontal icon spacing (in pixels) vertical icon spacing (in pixels) ferring to this module), and path name of the executable file. See also: Operating System DOS Memory JThis item lists the usage of the DOS memory, i.e. installed programs, used interrupts, etc. See also: DOS Memory info list Memory LXMS Memory (only available if installed) HThis item shows information about the installed XMS memory manager (like HIMEM) and XMS memory. See also: XMS Memory info list Memory LEMS Memory (only available if installed) HThis item shows information about the installed EMS memory manager (like EMM386) and EMS memory. See also: EMS Memory info list Memory LMemory Manager (only available if installed) JThis item shows information about a memory manager that supports a certain >IOCTL interface (Microsoft EMM386.EXE v4.45+ and CEMM v5.10+). See also: Memory Manager info list Memory LMicrosoft EMM386.EXE v4.45+ (only available if installed) KThis item shows information about later versions of Microsoft's EMM386.EXE. See also: Microsoft EMM386 info list Memory LNovell EMM386.EXE (only available if installed) ?This item shows information about the EMM386 from Novell DOS 7. See also: Novell EMM386 info list Memory LQuarterdeck QEMM-386 (only available if installed) 'This item shows information about QEMM. See also: QEMM info list Memory LHelix Software's RM386 / Micronics MICEMM (only available if installed) LThis item shows information about RM386 from Helix's Netroom, or MICEMM from some Micronics boards. See also: RM386 info list Memory LDOS Protected Mode Interface (DPMI) (only available if installed) 'This item shows information about DPMI. See also: DPMI info list Memory LNovell DOS Protected Mode Services (DPMS) (only available if installed) LThis item shows information about DPMS from Novell DOS (which also run under MS-DOS). See also: DPMS info list Memory LVirtual Control Program Interface (VCPI) (only available if installed) LThis item shows information about the VCPI (which offers more than just mem- Jory control, but as it is implemented by memory managers like EMM386, it's listed here). See also: VCPI info list Memory Memory Map 6This item shows an overview over your system's memory. See also: Memory Map info list Memory Memory Speed GThis item shows speed comparisons of the parts of your system's memory. LThe speed test won't run under OS/2 or Windows 386-mode because you wouldn't $get reasonable timing results there. See also: Memory Speed info list Memory RAM/ROM Extensions BThis item shows supposed RAM and ROM extensions (like a VGA BIOS). See also: RAM/ROM Extensions info list Memory LMemory Dump Alt-D JThis item opens a window where you can browse through your system's memory (the first MB). See also: The memory dump window Memory DOS Memory IThis gives somewhat like the MEM command an overview over free memory :and the installed programs, plus the interrupts they hook. Displayed in the table are Total free memory and largest free block for Lboth low DOS (conventional) and upper (UMB) memory, and both together; these Kincluded is the memory used by agSI and its environment itself (which would "be free if agSI were not running). UMBs linked? Tells the UMB link state, that is, whether UMBs are searched Kwhen a memory block is allocated. Normally "No", but the LOADHIGH (LH) com- "mand sets it temporarily to "yes". KNote that UMBs are only present in DOS 5 and above, in an OS/2 DOS session, !or with some memory managers (?). The list lists the memory control blocks (MCBs) and their owners, with its Jstart segment (hex), the size (in bytes), the owner (DOS, the program, En- Jvironment of ..., "free" or ?), the command line (where applicable) or the Gowner (if environment; in hex), and (in the lines following) the hooked interrupts (in hex). JThe list includes the HMA (High Memory Area) at segment FFFFh (if used) if Ka known scheme is used for its control blocks, i.e. under DR-DOS/Novell DOS Land MS-DOS 7 (Windows 95), showing offset, size, and usage (MS-DOS: only ID, =usually "MS"; under Novell DOS, probably not the DOS kernel). INote that, though added to "free memory", the blocks used by agSI are not @displayed as "free", but just like other programs as "AGSI". IUnder DOS 4 and above, the first DOS Data block (in low as well as in UMB Hmemory) is separated into sub-blocks, listing stuff from the CONFIG.SYS, Jalso are DOS-owned blocks displayed as either "Code" or "Data"; if you get K"DOS: ?x?", this is an unknown code letter x (not "C" or "D"). Novell DOS 7 Kalso uses some blocks (in upper memory) like normal programs using the name I"DOS", and "DOS7:Data" shows device drivers in upper memory; Novell DOS 7 .uses a different method here than MS-DOS does. K(What looks like an IFS driver "O.SYS" under MS-DOS 7 / Windows 95, is rep- Lorted by MEM as "relocated EBIOS data", den "IFS driver" DRVSPACE as "sector Kbuffer", and an unnamed IFS driver as "block device tables" (so is it on my Hsystem). It seems DOS7/Win95 ignores the Name field in the MCB for these ,special uses and leaves whatever was there.) See also: Memory )XMS Memory, eXtended Memory Specification HIn opposite to normal Extended Memory, XMS provides controlled using and Jsharing extended memory via EMB's (Extended Memory Blocks) and works (like IEMS) with handles given to an application by the XMS manager (e.g. HIMEM. 4SYS), but is not accessible only in pages, like EMS. Following items are displayed: XMS specification version driver version (revision) A20 address line status (on or off; may be switched off to emulate an 58088/8086 and is normally on today (on 286+ systems)) HMA existing? (to see if it's used by DOS, see OS/In HMA?) total available XMS memory (in kbytes) the largest free block of XMS memory available (in kbytes) +If XMS 3.0+ is installed, on a 386+ system: total available SXMS memory (with 32bit access; in k) the largest free block of SXMS the physical address of the highest byte in memory :(that's at least what it should be I only get 00000000). JSXMS is "Super XMS" and an extension to the normal XMS specification which Auses 32bit registers thus allowing more than 64 MB of XMS memory. 4If HIMEM.SYS (or a compatible driver?) is installed: handler (/MACHINE switch) list AT A20 switch time: Tells the time a switch of the A20 address line takes (on ATs): Fast, Medium, or Slow. ;If HIMEM.SYS v3.09 (from MS-DOS 6.0) or above is installed: address of handle table version flag (hex; 01 in v3.09 and 3.10) maximum number of handles (/numhandles= switch, default 32) number of currently used handles, and a list of these handles: handle number (hex) starting linear address in kBytes (hex) size (in k) "locked" if this block is locked, i.e. may not be moved FNote that if you are running Windows, XMS version may be "2.0" (driver L2.05), but HIMEM 3.09+ tells the handles; these will all be marked as "used" even if their size is 0 k. ) Note: It seems the Microsoft programmers can't make their mind up which Lversion format (BCD or binary) to use: the HIMEM.SYS of MS-DOS 6.22, the MEM Kcommand of which tells "3.16" (i.e. binary interpretation), explicitly con- Itains a string with "3.10" (i.e. BCD), and that's what agSI reports; how- Lever, inside a Windows 95 (Preview) DOS box, the value would be a "3.5F" BCD 1which is "3.95" (like with some other modules)... See also: Memory Handler (/MACHINE: switch) !Code Number System type 0at 1 IBM AT or 100% compatibles ps2 2 IBM PS/2 *ptlcascade 3 Phoenix Cascade BIOS (hpvectra 4 HP Vectra (A & A+) $att6300plus 5 AT&T 6300 Plus acer1100 6 Acer 1100 +toshiba 7 Toshiba 1600 & 1200XE 'wyse 8 Wyse 12,5 MHz 286 tulip 9 Tulip SX "zenith 10 Zenith ZBIOS 1at1 11 IBM PC/AT (alternate delay) 1at2 12 IBM PC/AT (alternate delay) css 12 CSS Labs 1at3 13 IBM PC/AT (alternate delay) philips 13 Philips fasthp 14 HP Vectra ibm7552 15 IBM 7552 $bullmicral 16 Bull Micral 60 dell 17 Dell XBIOS 1(Taken from the MS-DOS 6.0 online documentation.) )EMS memory, Expanded Memory Specification GThis is a standard by Lotus, Intel and Microsoft often referred to as L'LIM' for providing more memory for applications by mapping in some memory Hin 16 or 64k pages to an address (called the page frame) within the 1meg Haddress space in order to enable even normal programs to use the memory. KThis works even on PCs and XTs with an 8088/8086 with special memory cards, Eor with an EMS software emulator for 80386+ systems, e.g. EMM386.EXE. "The following items are displayed: LIM EMS specification version (usually 3.2 or 4.0) !(most applications only need 3.2) total EMS memory (in k) free EMS memory (in k) page frame address (hex), ,the segment where EMS pages are made visible the number of active handles the handles themselves, their name (if any; not LIM 3.x), and their size (in k) See also: Memory Memory Manager IThis is displayed when a (expanded) memory manager supporting these three LIOCTL calls is installed (EMM386 4.45+, CEMM 5.1+, QEMM-386 6+); this inter- @face is mainly intended for use by Microsoft Windows at startup. KThis interface seems not to be supported this way by EMM386 from Novell DOS IThese calls seem to be available also when no EMS is provided, then using !"EMMQXXX0" instead of "EMMXXXX0". The items displayed are: (command 0) Version Flag? (0022h for CEMM 5.11, 0025h for MS EMM386 v4.45/4.48) Private API entry point (command 1)# Physical (absolute) address of Global EMM Import Structure (used for Windows at startup) Version of EMM Import Structure: v1.00 contains only EMS information (Windows 3.0+) v1.10 contains UMB/XMS/HMA/EMS information (Windows 3.1) v1.11 is v1.10 plus memory manager maker/product name (command 2) EMM version (command 4)* If there's code/data of EMM386 in the UMB, then these two lines tell the 3segment and size (in paragraphs) of this code/data. KNote: It seems these calls don't return meaningful values under Windows 95. Detection: IOCTL "EMMXXXX0" See also: Memory Microsoft EMM386.EXE KThis is Microsoft's Expanded Memory Manager (which also implements UMBs) in Iit's newer .EXE versions (EMM386 version 4.20 and above) as it comes with LWindows 3.1 (version 4.44) and MS-DOS 6.0 (version 4.45) (or MS-DOS 6.2 with v4.48). Displayed are: the version the entry point the status (ON, OFF, or AUTO) whether a Weitek coprocessor is present if yes: whether Weitek support is on or off ) (if it could be found out: the segment of the entry point is scanned for Ithe string 'MICROSOFT EMM386 ' (11 blanks) which is followed by Jthe version string, e.g. '4.48', 9 blanks and an ASCII zero I don't know Lif this is and will be true for all versions, but it is the case in all that !are known to me 4.4? to 4.95).) LDetection: Int67/FFA5h (this call is available even if EMM386 is not provid- ing EMS) See also: Memory Novell DOS EMM386.EXE HThis is Novell's edition of a not only Expanded Memory Manager, but also 7includes functionality Microsoft included in HIMEM.SYS. Displayed is: the signature (should be EDC0h) the EMM386 variant: 2 = DPMI/VCPI disabled 3 = DPMI/VCPI enabled the version? (0300h=3.00, but also for version 3.03...) the segment of EMM's low-memory stub EIf the Video Memory Space Control call is supported (it normally is); like with the command MEMMAX /V: the segment of reserved video memory the segment of used video memory the segment of the first upper memory control block (MCB) KThere is also a state record available through IOCTL "EMMXXXX0" which, how- Kever, contains the above signature EDC0h plus 60 other bytes the meaning of ?which is yet unknown (on my system: most 0, some FFh, one 1)... Detection: Int2F/12FFh,BX=0106h +BX=0006h for the Video Memory Space Control See also: Memory Quarterdeck QEMM-386 KQEMM386 is a memory manager (like EMM386 that comes with DOS) with some en- 3hanced features. Displayed are the following items: API entry point version status (ON/OFF, AUTO) memory total and free maximum physical address first MCB in HIRAM (i.e. first program address used in upper memory) Memory type map (first MB) memory access status (first MB) memory usage statistics Stealth type: either 0=none, M=Memory, F=Frame, P=Protect, or unknown; GStealth is a technique to place upper memory "above" the ROM BIOS, thus %"hiding" the BIOS from direct access. Detection: IOCTL "QEMM386$" See also: Memory 1Helix Software's Netroom RM386 / Micronics MICEMM IRM386 is a memory manager (like EMM386 that comes with DOS) with some en- Ghanced features (MICEMM is an OEM version(?) for some Micronics mother- boards). "Displayed are the following items: Code segment of RM386 size (code plus data) allocated EMS handles (if any) global I/O port trapping, and interrupt used for this Global flags: V86 mode 386 or higher CPU A20 enabled at start-up large frame PS/2-style A20 control HMA in use XMS present using XMS driver memory A20 global enable flag A20 flag and many other configuration flags, if set Detection: Int67/5BF0h See also: Memory #DOS Protected Mode Interface (DPMI) JMainly developped internally by Microsoft for use in Windows 3.0, but pub- Ilished 1990 in a DPMI Comittee (with Borland, Intel, Eclipse, IBM, Lotus, LPharLap, Quarterdeck and Rational Systems). DPMI is, basically, an interface Lfor protected mode services for protected mode programs; it is more flexible and far more powerful than VCPI. 0Displayed is from the real-mode Int2F interface: DPMI version (widely spread is 0.90, OS/2 implements 0.95) type (the 'bandwidth') of applications supported (32bit or only 16bit) CPU type told by the DMPI server: 286, 386, or 486; Pentiums seem to be reported also as 486-type. IUnless disabled (see command line, Options dialog), these are the results Hfrom switching to protected mode and gathering some information from the protected mode API of DPMI: DPMI version (should be the same as above) flags: eight (of 16) bits with the following meaning: implementation type: same as 'bandwidth' above virtual8086 mode: if not, DPMI switches to real mode for interrupts virtual memory support (yes or no) bit 3 is reserved (undefined), bits 4..15 reserved (zero) buffer size for state saving: when using "raw" switching between real and Eprotected mode, the state of CPU/DPMI is needed to be saved when this field is non-zero base interrupt of master and slave virtual interrupt controller (hex); see also VCPI entry point addresses for both real and protected mode for: save/restore state (if buffer size above is 0, this call does nothing) raw mode switch largest available block of DPMI memory, in bytes +If virtual memory is supported (see above): page size (in bytes) maximum unlocked page allocation maximum locked page allocation total linear address space free linear address space total unlocked pages free pages total physical pages size of swap file/partition' HIf installed/supported, the following vendor-specific APIs are detected: "MS-DOS" MS Windows, 386MAX v6.00+ and Novell DOS EMM386 "386MAX" 386MAX v6.00+ "HELIX_DPMI" Helix Netroom's DPMI server "Phar Lap" Phar Lap 286|DOS-Extender RUN286 Detection: Int2F/1687h See also: Memory )Novell DOS Protected Mode Services (DPMS) LDOS extension services from Novell DOS 7.0 which allow drivers/programs/TSRs Lto use some extended memory, leaving more low or UMB memory free (also works *under MS-DOS, and comes with Stacker 4.0). ;DPMS Server Structure (from the Novell DOS 7.0 release on): DPMS signature and version (should be "DPMS 1.00") OEM server name and version ("Novell 1.02" in the (German) general re- lease version) CPU type (286, or 386+; also higher values allowed) Flags: none, or some of the below: fast processor reset available (286 only) DPMS server is enabled memory is remapped From registering a client and calling the API: largest free memory block accessible via DPMS largest mappable block size (if supplied) actual API addresses (Real, 16bit and 32bit Protected Mode) E(returned by "Register Client" are pieces of code which normally con- tain the following: CALL FAR XCHG BX,BX $RET or RETF < to be set by client Awhere is a FWORD PTR (xxxx:xxxxxxxx) in the 32bit case; all 5this, by the way, occupies 8 (32bit: 10) bytes each.) KRegistration Structure (in pre-Novell DOS 7.0 beta specifications, but also Lsupported in Novell DOS 7.0 general release, but not anymore in the DPMS.EXE "v1.1 from the v3 update (D70U03)): DPMS version Server OEM name (max 8 characters) CPU type (286, or 386 or higher) real-mode and 16bit protected mode API entry point largest free memory block accessible via DPMS Detection: Int2F/43E0h See also: Memory (Virtual Control Program Interface (VCPI) IThis is a standard mainly for using 80386/486 several programs working in Iprotected mode (DOS extenders, multitaskers, memory managers,...) without Jinterfering each other, declared 1989 by some software companies under the Jlead of PharLap (writing DOS-Extenders) and Quarterdeck (who presented the Imultitasker DESQview and the memory manager QEMM), and supported today by 9many memory managers, etc, also in DOS 5.0+'s EMM386.EXE. Displayed are: VCPI specification version (normally 1.0) the maximum physical memory address /(a 32bit hex value, 00FFF000 on my 16MB system) the number of free 4K pages and its equivalent in kbytes the interrupt vector mapping of the Interrupt Controller 8259, the master F(for IRQ0-7) and the slave (IRQ8-15), which is connected to the master Hvia IRQ2, i.e. the first interrupts they use (remapping of the master is Gnecessary to avoid CPU exceptions messing with the hardware interrupts; Fhowever, Microsoft's EMM386 seems to use the real-mode standard 08 for the master). the Virtual8086-mode segment to physical address mapping, which displays Ewhich physical addresses are accessed when a V86Mode program accesses Hits memory; usually, the main memory is not remapped, but, for instance, FUMB is provided by mapping in extended memory, and the MS-EMM386 hooks Fthe reset address in the ROM-BIOS (F000:FFF0) to itself by remapping a small segment. the value of Control Register 0 (CR0), plus the meanings of the bits set; Ecapital letters tell the abbreviation of the bit name. The used bits: b31, PG: paging enabled b29, WT: write through b18, AM: align mask set b16, WP: write protect enabled b6, NE: numeric exceptions b4, ET: extension type b3, TS: task switched b2, EM: emulate coprocessor b1, MP: monitor coprocessor b0, PE: protected enabled ( virtual 8086 mode) Detection: Int67/DE00h See also: IRQ assignments Memory Memory Map Not yet implemented...... See also: Memory Memory Speed HThis page compares the read access speeds of the various regions of your *system's memory below 1 MB in 16-KB steps. KDisplayed is the start (decimal in KB and the hexadecimal segment start ad- Ldress), the size (in KB) of the same speed (within a certain tolerance), the Lbandwidth (8, 16, or 32-bit), and the relative speed (percentage and a bar), Kthe fastest being 100% (concerning the fastest possible way of access, i.e. L16 bit for antique 286's and 32 bit for the rest; please allow timing-depen- 0dent differences in the range of a few percent). KPlease note: The bandwidth is called lower than 32-bit if, within a reason- Hable tolerance, the 32-bit throughput is NOT twice the 16-bit throughput H(analogue for 16 and 8). However, especially on modern computers, 16-bit Kaccess is FASTER than the half of 32-bit access due to chipset-internal op- Jtimizations, so don't worry if your brand-new P6 shows regions of 8 or 16- "bit memory, that's not the case... GAlso note that the graphics region of video memory (A000h) may be shown Lpretty slow, even on modern cards... probably because *reading* video memory :is not needed to be fast, writing is all that's important. LThe speed test won't run under OS/2 or Windows 386-mode because you wouldn't $get reasonable timing results there. See also: Memory RAM & ROM Extensions LThis displays the addresses and sizes of RAM and ROM extensions, such as VGA LBIOS ROM (usually C0000-C7FFF); your video card's display memory is (normal- ly) not displayed. BUMBs (Upper Memory Blocks) are usually displayed as RAM extension. FIf for an expansion ROM (for a hard disk controller, for instance) the Ichecksum check is wrong, this may be caused by using parts of the address Jspace of the ROM as UMB (or coincidentally there are the same bytes at the Istart of a 16K segment as are used for ROMs, but that's pretty unlikely). JNote that a ROM extension may also appear as a RAM extension [I don't know yet why...]. See also: Memory LMouse Driver (only available if installed) =This item shows information about the installed mouse driver. See also: Mouse driver info list Software LAlternate Multiplex Interrupt Spec. (AMIS) (only available if installed) HThis item shows information about the AMIS (which use Int2Dh) which were& Lproposed by Ralf Brown (see also the Interrupt List) due to the multitude of 8programs using the original Multiplex Interrupt, Int2Fh. See also: AMIS info list Software LAdvanced Power Management (APM) (only available if installed) 4This item shows information about the APM functions. See also: APM info list Software LAPPEND (only available if installed) 9This item shows information about the DOS utility APPEND. See also: APPEND info list Software LASSIGN (only available if installed) 9This item shows information about the DOS utility ASSIGN. See also: ASSIGN info list Software LCOMM-DRV (only available if installed) LThis item shows information about the universal serial communications driver COMM-DRV. See also: COMM-DRV info list Software LFOSSIL (only available if installed) LThis item shows information about the communications driver standard FOSSIL. See also: FOSSIL info list Software LHyperWare Products (only available if installed) HThis item shows information about products from HyperWare, Inc., such as HyperDisk HyperStb HyperScreen HyperKey+ AX=CAFEh, BX=5021h ('P!') See also: Software RAHMEN KThis is my own little utility ("Rahmen" (German) = "frame") which grabs the Lkeyboard interrupt (09h) to offer frame (and other useful) characters on the Cnumeric pad, switched by using Ctrl-NumLock and Shift-Ctrl-NumLock. 'The items of information displayed are: Version segment of resident code flag active / deactivated current assignment The available assignments are: -->> Ctrl-NumLock -->> 3-0- -1- -2- -3- -4- -5- -6- 57 8 9 54 5 6 51 2 3 50 , 255 255 <<-- Shift-Ctrl-NumLock <<-- &Detection: Int2F/FACEh/BX=523Fh ('R?') => AX=CAFEh, BX=5221h ('R!') See also: Software SETVER ISETVER is used in DOS 5 and above for telling applications wrong DOS ver- Hsions if these applications refuse to work with higher DOS versions than Lthey were programmed for. (This was, with an internal list, possible also in 1DOS 4, but not supported by an external program.) LDisplayed is also the list of program names and their associated "fake" ver- 9sions (for MS-DOS 5.0 and above, Novell DOS 7, and OS/2). Detection: IOCTL "SETVERXX" See also: Software SHARE JThe program that controls file accesses by more than one program at a time I(file sharing); it is normally used in networks and multitasking environ- Kments (so OS/2 version 2 implements SHARE functionality within its DOS ses- Jsions); FCB support for media greater than 32 MB for MS-DOS 4.x was imple- *mented in SHARE (additionally, separated). IDisplayed are the segment of SHARE.EXE and a list of the files loaded via1 JShare (if any), and if non-zero the network machine number (or virtual1 Hmachine ID under Windows enhanced-mode) and the number of locks for this file. KYou can find more information about the sharing record and the locks in the 5System File Tables list in the Operating System menu. JNote (differences in Novell DOS SHARE): the segment may be 0, and the file :names are not in full path name but like "C:AGSI .OVR". Detection: Int2F/1000h See also: Software +TaskMAX (DR-DOS)/TaskManager (Novell DOS 7) IThis is DR-DOS' (and Novell DOS') task manager; displayed are its version L(DR-DOS 6.0's TaskMax tells "1.00", NWDOS' "2.55" -?), the number of maximum Jsimultaneous tasks, the number of the currently active tasks, and how many 8EMS pages are told the tasks to be free (via Int67/42h). Detection: Int21/2700h See also: Software TBSCANX JTBScanX is a resident virus scanning module by Frans Veldman. Programs may Lperform virus checks on themselves, other program files, or their data files by invoking the TBScanX API. HDisplayed are the version, the status (on or off), and the number of the 'virus signatures that are searched for. Detection: Int2F/CA00h/BX='TB' See also: Software Virtual DMA Specification (VDS) LSupports DMA (Direct Memory Access) virtualisation under multi-tasking envi- 4ronments, especially when the 386+'s paging is used. JThis info pane tells the VDS version (currently 1.00), the product and its Krevision (see below), the maximum DMA buffer size (in bytes), and the flags (see below). AVDS is supported by the following products: product code: Microsoft's EMM386.EXE 0001h Novell's EMM386.EXE 0EDCh Microsoft Windows, enhanced mode 0003h IBM OS/2 (2.x?) 0300h Qualitas' 386MAX 4560h V Communication's Memory Commander 4D43h ('MC') Quarterdeck's QEMM-386 5145h ('QE') Helix's Netroom RM386 524Dh ('RM') Quadtel's QMAPS and Hewlett-Packard's HPMM.SYS 0000h KIf you get "? (xxxx)", VDS is supplied by a to me yet unknown program which Lidentifies itself with the hex number in brackets; if you know what it could be, please tell me. Flags: b0: system has a PC/XT bus (DMA in first megabyte only) b1: physical buffer/remap region in first megabyte b2: automatic remap enabled b3: all memory is physically contiguous other bits: reserved Detection: Int4B/8102/DX=0 See also: Software Others LThese are other programs/services where there is no other information avail- Kable but the fact that they are installed (and maybe their version; most of ?them detected via their Int2F (Multiplex Interrupt) functions). JAs they are listed in alphabetical order, they may seem a little confusing concerning their functions. %Detected in this version of agSI are: 4DOS KSTACK.COM After Dark DOS ANSI.SYS Banyan VINES 4.0+ Borland DPMILOAD Borland RTM.EXE Borland TDX Btrieve Multi-User c't Warmboot driver -CAS (Communication Application Specification) &CiriSOFT 2M (maybe other manufacturer) Critical Error Handler DELWATCH (Novell DOS) DESQview DESQview QEXT.SYS DESQview/X DIMWIT DISPLAY.SYS DOS Extender DOSKEY DOSSHELL DoubleDOS DRIVER.SYS support EGA.SYS F-PROT VIRSTOP.EXE FLU_SHOT+ FN32 32CHAR TSR Frank Kintrup TSR utilities GRAFTABL.COM GRAPHICS.COM IFSHLP.SYS Intel IPI / LaserPort INTERLNK LapLink RemoteAccess LapLinkCore LapLink RemoteAccess Blackbird LapLink RemoteAccess Redirector LapLink RemoteAccess Compression LASTBYTE LASTBYTE HIGHUMM License Server API MICRO.EXE MS Profiler (PROF.COM/VPROD.386) MTEZ XpressFax MX5 Extended FOSSIL Nanosoft TurboNET Network Redirector NLSFUNC PC Tools BACKTALK PC Tools COMMUTE PC Tools CPTASK PC Tools DATAMON PC Tools DESKTOP PC Tools DRIVEMAP PC Tools PCShell $PC Tools Scheduler (CPSCHED/DESKTOP) #PC Tools/DOS 6 VSAFE/VWATCH/VDEFEND pcANYWHERE IV large/small host Personal Measure ASPIHOOK Personal Measure PMEASURE.EXE Personal Measure Hook Module PERUSE POWER.EXE PRINT PrintCache PCACHE.EXE PrintScreen QMR Quick Mouse Reset Quarterdeck memory drivers RECEIVER.COM REDIRIFS REDVIEW SCRIPT (Novell DOS) SCSI-CAM (Common Access Method) SDRes SMD / PrecisePoint SoundBlaster Speech Driver SpaceManager SuperStor Pro 2XON.COM Task Switcher API THELP Topware Network Operating System TSENGP.COM TurboPower TSR(s) UIH (Utilities im Hintergrund) WINGO WHOA! XMA2EMS ZyXEL ZFAX ??? on Int2F Mux No. XXh See also: Software #The above information is taken from )a) the 4DOS manual (4DOS and 4DOS KSTACK) b) my own experiments %c) the book 'DOS 5 f r Programmierer' d) Ralf Brown's Interrupt List J4DOS is a (shareware) command line interpreter replacement for COMMAND.COM /by JP Software, listed with its version number. See also: More about 4DOS. Detection: Int2F/D44Dh See also: other programs Software 4DOS KSTACK.COM EThis is a resident utility from 4DOS which may simulate keystrokes to .applications, using the 4DOS KEYSTACK command. Detection: Int2F/D44Fh See also: other programs Software E4MAP is a keybinding program for 4DOS by Ho-Ping Tseng which lets you ?perform some operations at the command prompt at one keystroke. Detection: Int2F/F000h See also: other programs Software After Dark for DOS JAD-DOS is the DOS version of the After Dark screen blanker for MS Windows. Detection: Int2F/C000h-FF00h See also: other programs Software ANSI.SYS IANSI.SYS is a program for more functionality in video and keyboard usage; Bthere are also other similar utilities, like EANSI, NANSI, NNANSI. EDetection: Int2F/1A00h (original ANSI.SYS only under DOS 4 and above) See also: other programs Software Personal Measure KThe detected parts of the Personal Measure system hardware activity monitor &from Spirit of Performance, Inc., are: ASPIHOOK.SYS, a device driver for monitoring SCSI activity through an ASPI host manager; PMEASURE.EXE, a TSR for monitoring system hardware activity; Hook Module: the Personal Measure uses an extensible series of modules to Ghook into various operating system interfaces and monitor system calls. Detection: Int2F/C0-FFh See also: other programs Software -Advanced Power Management Specification (APM) LThis specification defines an interface to APM-functions mainly on notebooks Mand on modern "green" systems which enables control functions for energy-sav- Ning methods (especially useful for notebooks), to, for instance, switch screen -and hard disk off when nothing is being done. 1The following items are displayed (if supported): Version Flags: a hex value where the bits mean: b0: 16-bit protected mode interface supported b1: 32-bit protected mode interface supported b2: CPU idle call reduces processor speed b3: BIOS power management disabled b4: BIOS power management disengaged others: unknown/reserved AC line status: off-line, on-line, on backup power, or unknown battery status: high, low, critical, charging, or unknown remaining battery life: percentage, or unknown; minutes/seconds for APM 1.1 OEM: hex word; known OEMs: 534Ch = Intel SL Enhanced, 4850h=HP Detection: Int15/5300h See also: Software Banyan VINES DTells the interrupt of Banyan's network software, if it's installed. Detection: Int2F/D701h See also: other programs Software Borland DPMILOAD KThe DPMI Loader from Borland Pascal 7.0 and C++; should only be loaded when $a Pascal/C++ DPMI program is active. $***DISABLED: Resulted in DPMI error. 2Detection: Int2F/FB42h/0001h (Protected Mode only) See also: other programs Software Borland Run-Time Manager RTM.EXE FThe Run-Time Manager for DPMI programs from Borland Pascal 7.0 or C++. 1Detection: Int2F/FB42h/0001h (nur Protected Mode) See also: other programs Software Borland TDX 5The DPMI program version of Borland's Turbo Debugger. $***DISABLED: Resulted in DPMI error. 2Detection: Int2F/FB43h/0100h (Protected Mode only) See also: other programs Software Btrieve Multi-User Detection: Int2F/AB00h See also: other programs Software CiriSOFT 2M L2M is a freeware utility for high-capacity disk formatting (max. 1886 k on a " HD disk) by Ciriaco Garc a de Celis. HDisplayed is the installation test signature like "CiriSOFT:2M:1.3", for )CiriSOFT as manufacturer and version 1.3. *Detection: Int2F/C0h-FFh/ES:DI=1492h:1992h See also: other programs Software .Communicating Applications Specification (CAS) +A standard access interface for fax modems. Detection: Int2F/CB00h See also: other programs Software Critical Error Handler IThis is used for extended error message information when a critical error ,occurs, e.g. installed with a CD-ROM driver. Detection: Int2F/0500h See also: other programs Software Novell DOS DELWATCH.EXE ?DelWatch is Novell DOS's tool to track and undo file deletions. Detection: Int2F/10FEh See also: other programs Software DESQview LDESQview is a multitasking environment under DOS from [do I remenber right?] Quarterdeck. Detection: Int21/2B/CX:DX='DESQ' See also: DESQview QEXT.SYS DESQview/X other programs Software DESQview QEXT.SYS "A driver that comes with DESQview. Detection: Int15/11DEh See also: other programs Software DESQview/X DVDOS4GX.DVR LThis is a driver from Quarterdeck's own multi-tasking operating system which evolved from DESQview for DOS. Detection: Int15/BFDEh See also: other programs Software KDIET is an executable-file compression program, which also may be installed 4resident to compress and decompress text/data files. @Detection: Int21/4BF0h (in Overlay Mode (?)), 37D0h, normal mode See also: other programs Software DIMWIT ADIMWIT is a freeware Windows-aware screen blanker by Larry Board. Detection: Int2F/C0-FFh See also: other programs Software DISPLAY.SYS 3Driver for codepage management (DOS 3.3 and above). Detection: Int2F/AD00h See also: other programs Software DOS Extender +Displayed when a dos extender is installed. GSupported or soon to be supported by Phar Lap, Rational, Ergo, and IGC. Detection: Int2F/F100h See also: other programs Software DOSKEY JThe command line editing enhancement of DOS 5+ [which does not at all give (the same functionality as 4DOS does...]. Detection: Int2F/4800h See also: other programs Software DosShell JMicrosoft's simple desktop for non-high-end users (those who don't use the Bcommand line or those who can't afford a PC which runs Windows...) IDosShell (at least in versions 5+) is not recognized if task-switching is not activated (?). Detection: DOS 4.x: Int2F/1900h DOS 5+: Int2F/4680h See also: other programs Software DoubleDOS +DoubleDOS is a DOS multi-(or dual?) tasker. Detection: Int21/E400h or F400h See also: other programs Software DRIVER.SYS support ITells whether the internal support code used by DRIVER.SYS for additional 4drive handling is present; usually always displayed. Detection: Int2F/0800h See also: other programs Software EGA.SYS LFor graphics screen support under the Dos Shell or Windows, from Windows 3.x >or DOS 5.0+, displayed together with its version and revision. $Detection: Installation: Int2F/BC00h Version: Int2F/BC06h See also: other programs Software F-PROT VIRSTOP.EXE KF-PROT (with its resident VIRSTOP.EXE) is a virus/trojan protection package by Fridrik Skulason. Detection: Int2F/4653h/CX=9 See also: other programs Software FLU_SHOT+ KFLU_SHOT+ is an antivirus/antitrojan program by Ross M. Greenberg and Soft- ware Concepts Design. Detection: Int21/FF0Fh See also: other programs Software FN32 32CHAR TSR DFN32 is a TSR which supports 32 character filenames under PC/MS-DOS. Detection: Int2F/C0-FFh See also: other programs Software Frank Kintrup TSR Utilities FThe following TSR utilities by Frank Kintrup (Shareware) are detected: ASCII.COM ASCII table CLOCK.COM clock PCALC.COM calculator SCRSAVE.COM screen saver UNDEL.COM undelete CDPLAY.COM CD player KDisplayed is also the version and Int2Fh multiplex number and resident code segment. Detection: Int2F/C0-FFh BX='FK' See also: other programs Software GRAFTABL.COM BLoads the extended character table for use in (CGA) graphic modes. Detection: MS-DOS: Int2F/B000h DR-DOS: Int2F/2300h Novell DOS: Int2E/2E00h See also: other programs Software GRAPHICS.COM !Used for graphic screen printing. ,Detection: DOS 5+: Int2F/AC00h (documented) 8DOS 4.x: Int2F/1500h (undocumented, also used by MSCDEX) below 4.x no installation test /[So much about cooperation inside Microsoft...] See also: other programs Software IFSHLP.SYS JIFSHLP is a support driver for the IFS Manager (for 32-bit file access) of 5Microsoft Windows for Workgroups 3.11 and Windows 95. Detection: IOCTL "IFS$HLP$" See also: other programs Software &Intel Image Processing Interface (IPI) LaserPort Interface LThis is displayed if either of the above products is installed; I don't know how to decide which it is. Detection: Int2F/CD00h See also: other programs Software INTERLNK API JMicrosoft's link program (for notebook desktop, for example) which comes bundled with MS-DOS 6.0. Detection: Int2F/5600h See also: other programs Software LapLink RemoteAccess (LLRA) AThe following components are detected, together with the version: LapLinkCore (LLRA1.EXE) Blackbird (LLRA2.EXE) Redirector (LLRA3.EXE) Compression (LLRA4.EXE) INote: LapLink components are installed in the order listed above, but not necessarily all four. Detection: Int2F/C0-FFh See also: other programs Software The Last Byte - LASTBYTE.SYS LLASTBYTE.SYS is part of The Last Byte (tm) an Upper Memory Manager (share- Hware) by Key Software Products, which provides use of the upper memory Hfrom the physical installed memory, and does not map EMS-like pages like KEMM386 (if the chip set is supported). Even HIMEM.SYS may be loaded high... Detection: IOCTL "LA$TBYTE" See also: LASTBYTE HIGHUMM other programs Software The Last Byte - HIGHUMM.SYS CHIGHUMM.SYS is part of The Last Byte and may only be installed when HLASTBYTE.SYS is installed. It provides use of LastByte's upper memory in 7DOS-compatible style with DEVICEHIGH and LOADHIGH (LH). Detection: IOCTL "KSP$UMM" See also: LASTBYTE other programs Software License Service API KThis line may occur several times, because there are several licensees pos- 7sible; the number of the license is displayed (in hex). JThe License Service API is being maintained by Microsoft but is being sup- Gported by a large number of companies including Apple, Banyan, DEC, HP, JLotus, Microsoft, Novell, Software Publishers Association, and Wordperfect (not a complete list!). Detection: Int2F/7000h See also: other programs Software MICRO.EXE IMICRO.EXE is a TSR of the Microsoft Mail part of Workgroup Connection, an Dadd-on to MS-DOS 6.0 (planned to be bundled first, but some licensor (Novell?) did not allow that). Detection: Int2F/9400h See also: other programs Software *Microsoft Profiler (PROF.COM or VPROD.386) Microsoft's profilers. Detection: Int2F/4500h See also: other programs Software MTEZ XpressFax TSR (CLASS2) From a fax. Detection: Int2F/C000h-FF00h See also: other programs Software MX5 Extended FOSSIL IMX5 is a FOSSIL driver by MagicSoft which emulates MNP Level 5, and ships Kwith the MTEZ terminal program as MTEMNP.DRV (a TSR despite the .DRV exten- sion). Detection: Int14/E006h See also: other programs Software #Nanosoft TurboNET server/redirector HTurboNET is a NetBIOS-based file redirector and server by Nanosoft, Inc. 3Detection: Int2F/8000h (server), 8100h (redirector) See also: other programs Software KNDOS is Symantec's (Norton Utilities) licensed OEM version of JP Software's 4DOS. Detection: Int2F/E44Dh See also: other programs Software Network Redirector LListed when a network redirector is installed; also displayed under Windows. FDetection: Int2F/1100h (and 111Fh/5E03h, because 1100h interferes with CD-ROM) See also: other programs Software NLSFUNC FFor country-specific operations (these functions may also be installed Ewithin a DOS box under OS/2 and Windows without explicitly installing NLSFUNC). Detection: Int2F/1400h See also: other programs Software !PC Tools Programs (Central Point) BACKTALK: Detection: Int16/6969h COMMUTE: communication (e-mail, net,...). Detection: Int62/6262h CPTASK: task switcher. Detection: Int16/FF80h (v8.0+) DATAMON: Detection: Int16/FFA3h; Int2F/6284h (v7.0+) DESKTOP: Desktop with organizer, scheduler, diary, calculators,... Detection: Int16/FFA9h DRIVEMAP: Detection: Int16/FF70h (v8.0+) PCShell: Integrated utility-desktop: Filemanager,... Detection: Int16/FFDDh Scheduler: This may be CPSCHED or DESKTOP, when scheduler functions are !activated. Detection: Int16/FEEFh VSAFE/VWATCH/VDEFEND: Resident virus checkers, included in MS-DOS 6.0. See also: other programs Software pcANYWHERE IV 3This is a remote control and file transfer program. &Detection: Int21/2B/AL:BX:CX='DMApcAW' Siehe auch: sonstige Programme Software PERUSE LPeruse is a TSR that captures and saves screen information as it scrolls off 0the top of the screen, storing it in EMS or XMS. KPeruse is Copyright (c) 1994, Bob Flanders and Michael Holmes and was first 4Published in PC Magazine April 12, 1994 (Utilities). Detection: Int10/B0BFh See also: other programs Software POWER.EXE ?The power management program from MS-DOS 6.0, with its version. Detection: Int2F/5400h See also: other programs Software PRINT JDOS's program for printing in the background [did I hear anybody say some- thing about multitasking?] Detection: Int2F/0100h See also: other programs Software PrintCache PCACHE.EXE LPCACHE is the resident print spooler portion of PrintCache by LaserTools; it 4may use either memory or disk space to spool output. (For more information about cluster size, etc., see DPB info.) Media ID byte: The type of the disk in hex, plus an explanation, which is one of the following: 9Value Media type Sides Tracks Sectors Capacity =F0 " HD or ED 2 80 18 or 36 1440k or 2880k hard disk or ram drive